# US 2026/0017633 A1 · Product dispenser interfaces

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0017633 A1
- Document ID: US20260017633A1
- Status: Published application
- Kind: A1
- Application number: 19/264,448
- Filed: 2025-07-09
- Published: 2026-01-15
- Earliest claimed: 2024-07-09
- Applicants: Wayne Fueling Systems LLC
- Inventors: Harish Veeravalli; Murat Goksenin Guzel
- Web page: https://patentgrep.com/patent/US20260017633A1

## CPC

- G06Q 20/204: {comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/085: {involving remote charge determination or related payment systems}
- G06Q 20/145: {Payments according to the detected use or quantity}
- G06Q 20/202: {Interconnection or interaction of plural electronic cash registers [ECR] or to host computer, e.g. network details, transfer of information from host to ECR or from ECR to ECR}
- G06Q 20/341: {Active cards, i.e. cards including their own processing means, e.g. including an IC or chip}
- G06Q 20/387: {Payment using discounts or coupons (relating to marketing G06Q30/02)}
- G07F 13/025: {wherein the volume is determined during delivery}
- G07G 1/0009: {Details of the software in the checkout register, electronic cash register [ECR] or point of sale terminal [POS]}
- G07G 1/06: with provision for the noting of the money to be paid
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G07F: COIN-FREED OR LIKE APPARATUS (coin sorting G07D3/00; coin testing G07D5/00; {handling coins or paper currencies apart from payment activated apparatus G07D; payment architectures, schemes or protocols G06Q20/00})
- G07G: REGISTERING THE RECEIPT OF CASH, VALUABLES, OR TOKENS

## Abstract

A dispenser is provided and in one embodiment can include a point-of-sale (POS) application and a pump controller operably coupled to the POS application via a first communication interface configured to exchange pump service data with the POS application via a first virtualized TCP server communicably coupling the pump controller to the POS application. The dispenser can also include a payment mechanism including a payment data processor operably coupled to the POS application via at least one second communication interface configured to exchange system service data with the POS application via a second virtualized TCP server communicably coupling the payment data processor and the POS application. The pump service data and the system service data can be generated by the POS application responsive to one or more operations performed at the dispenser. Related methods, systems, and computer-readable mediums are also provided.

## Claims

### Claim 1

A dispenser, comprising:
a point-of-sale (POS) application;
a pump controller operably coupled to the POS application via a first communication interface configured to exchange pump service data with the POS application, the first communication interface configured to exchange the pump service data via a first virtualized TCP server communicably coupling the pump controller to the POS application; and
a payment mechanism including a payment data processor operably coupled to the POS application via at least one second communication interface configured to exchange system service data with the POS application, the at least one second communication interface configured to exchange the system service data via a second virtualized TCP server communicably coupling the payment data processor and the POS application, the pump service data and the system service data generated by the POS application responsive to one or more operations performed at the dispenser.

### Claim 2 (depends on 1)

The dispenser of claim 1, wherein the at least one second communication interface is configured to exchange the system service data in an EMV data format.

### Claim 3 (depends on 1)

The dispenser of claim 1, wherein a portion of the at least one second communication interface is configured to exchange the system service data in an encrypted data format.

### Claim 4 (depends on 1)

The dispenser of claim 1, wherein a portion of the first communication interface is configured to exchange the pump service data in a CAN bus data format.

### Claim 5 (depends on 1)

The dispenser of claim 1, wherein the first and second virtualized TCP servers are configured to exchange the pump and system service data via TCP data packets including JSON formatted messages.

### Claim 6 (depends on 1)

The dispenser of claim 1, wherein the POS application is installed on the dispenser and configured for use by a third-party different than a manufacturer of the dispenser, the POS application enabling pump and system service data exchange for the one or more operations performed at the dispenser that are customized for the third party.

### Claim 7 (depends on 1)

The dispenser of claim 1, wherein the pump service data includes data characterizing at least one of configuration data of the pump controller, a software or a firmware update of the pump controller, telemetry data associated with the pump controller, diagnostic data associated with the pump controller, and log file data associated with the pump controller.

### Claim 8 (depends on 1)

The dispenser of claim 1, wherein the pump service data is generated responsive to the one or more operations performed at the dispenser including at least one of authorizing, deauthorizing, starting, stopping, suspending, and resuming the dispenser.

### Claim 9 (depends on 1)

The dispenser of claim 1, wherein the pump service data is generated responsive to one or more pump service events associated with the one or more operations of the dispenser, the one or more events pump service including at least one of a state change of the pump controller, a status change of the pump controller, a current total volume of a dispensed product generated by the pump controller, a current total sale of a dispensed product generated by the pump controller, a final total volume of a dispensed product generated by the pump controller, a final total sale of a dispensed product generated by the pump controller, an alert generated by the pump controller, an error generated by the pump controller, or a data metric generated by the pump controller.

### Claim 10 (depends on 1)

The dispenser of claim 1, wherein the system service data includes data characterizing at least one of configuration data of the payment mechanism, a software or a firmware update of the payment mechanism, serial number data of the payment mechanism, status data of the payment mechanism, log data of the payment mechanism, device pairing data associated with the payment mechanism, and remote key injection data associated with the payment mechanism.

### Claim 11 (depends on 1)

The dispenser of claim 1, wherein the system service data is generated responsive to one or more operations performed at the dispenser including at least one of pairing a card reader of the payment mechanism with POS application, pairing a printer of the payment mechanism with the POS application, updating a driver of the payment mechanism, updating a firmware of the payment mechanism, and synchronizing clock data of the payment mechanism.

### Claim 12 (depends on 1)

The dispenser of claim 1, wherein the system service data is generated responsive to one mor more system service events associated with the one or more operations of the dispenser, the one or more system service events including at least one of an online event, an offline event, a status change event, a battery status change event, a network status change event, a reboot event, a software update completion event, and a log completion event generated by the payment mechanism.

### Claim 13 (depends on 1)

The dispenser of claim 1, wherein the dispenser is at least one of a petroleum fuel dispenser, an electric vehicle charger, an LNG dispenser, a CNG dispenser, and a DEF dispenser.

### Claim 14

A method, comprising:
receiving, by a POS application of a dispenser, first data characterizing an installation package of a payment mechanism of the dispenser, the payment mechanism including a memory and a payment data processor, the installation package including a signature file associating the installation package with a third-party corresponding to the POS application;
verifying the installation package based on the signature file;
generating, by the POS application, an update software request and transmitting the update software request to a first virtualized TCP server communicably coupling the payment data processor of the payment mechanism to the POS application;
generating, by the first virtualized TCP server, a software state request and transmitting the software state request to the payment data processor;
comparing, by the first virtualized TCP server, hashed data associated with application file data stored in the memory of the payment data processor to hashed data associated with files of the installation package;
transmitting, by the first virtualized TCP server, the installation package to the payment data processor for installation; and
initiating, by the payment data processor, a system service communication interface between the POS application and the payment data processor, the system service communication interface configured to exchange system service data therebetween via the first virtualized TCP server responsive to one or more operations performed at the dispenser.

### Claim 15 (depends on 14)

The method of claim 14, further comprising generating, by the first virtualized TCP server, a system information request and transmitting the request to the payment data processor; and responsive to receiving a system information response, generating, by the first virtualized TCP server, an application update status event and providing the update status event to the POS application, the update status event indicating an outcome of installing the installation package in the memory of the payment mechanism.

### Claim 16 (depends on 14)

The method of claim 14, wherein the system service data includes data characterizing at least one of configuration data of the payment mechanism, a software or a firmware update of the payment mechanism, serial number data of the payment mechanism, status data of the payment mechanism, log data of the payment mechanism, device pairing data associated with the payment mechanism, and remote key injection data associated with the payment mechanism.

### Claim 17 (depends on 14)

The method of claim 14, wherein the update software request defines a logical distribution path identifying a file location or directory path associated with a location of the installation package.

### Claim 18 (depends on 14)

The method of claim 14, wherein the first data is received via a memory device storing the installation package, the memory device communicably coupled to the POS application.

### Claim 19 (depends on 14)

The method of claim 14, wherein the first data is received via a cloud computing device associated with the third-party.

### Claim 20 (depends on 14)

The method of claim 14, wherein responsive to receiving the installation package at the payment data processor, the first virtualized TCP server is further configured to reset the payment mechanism and the payment mechanism is configured to reboot to install the installation package.
