Fuel dispenser user interface system architecture

• US 10,102,401 B2
• Filed: 10/19/2012
• Issued: 10/16/2018
• Est. Priority Date: 10/20/2011
• Status: Active Grant

• Current Assignee: Gilbarco Italia SRL (Vontier Corp.)
• Original Assignee: Gilbarco Incorporated (Vontier Corp.)
• Inventors: Carapelli, Giovanni
• Primary Examiner(s): Poinvil, Frantzy
• Application Number:
  US13/655,938
• Publication Number:
  US 20130103190A1
• Time in Patent Office: 2,188 Days
• Field of Search: 705 3- 44, 705 50, 235383, 713168
• CPC Class Codes: G06F 21/445 by mutual authentication, e.g. between devices or programs
• CPC Class Codes: G06F 21/82 Protecting input, output or interconnection devices
• CPC Class Codes: G06F 21/86 Secure or tamper-resistant housings
• CPC Class Codes: G07F 13/025 wherein the volume is determined during delivery
• CPC Class Codes: G07F 7/1033 Details of the PIN pad
• CPC Class Codes: G07F 9/006 Details of the software used for the vending machines
• CPC Class Codes: G07F 9/026 for alarm, monitoring and auditing in vending machines or means for indication, e.g. when empty

Abstract

A vending machine user interface can include a first controller operatively connected to an input device capable of receiving payment or account information. The first controller can, with another device, via a second controller, or otherwise, allow secure communication of data from the input device. The first controller, in this regard, can control the communication between the input device and the other device to protect the input device from unwarranted communication from the other device. The first controller can establish a secure channel with the other device using encrypted communications. The first controller, second controller, etc. can be connected to independent printed circuit boards (PCB). Activation of sensors connected to the PCBs can cause the first and/or second controllers to erase data necessary to ascertain/decode communications from the input device, such as encryption/decryption information, or may otherwise decommission the input device or a portion thereof.

Claims

1. A user interface for a retail device comprising:

at least one payment device configured to receive payment data associated with a payment card;

a first controller operatively connected to the at least one payment device and configured to receive the payment data associated with the payment card from the at least one payment device and to encrypt the payment data to create encrypted payment data;

a second controller separate from said first controller but operatively connected to the first controller, said second controller configured to receive the encrypted payment data from the first controller;

a housing, wherein the first controller is affixed to the housing;

at least one sensor connected to the first controller and the housing, the at least one sensor being configured to detect separation of the first controller from the housing, wherein activation of the at least one sensor causes the user interface to become inoperable; and

a display for the retail device operatively connected to the second controller, wherein the second controller is configured to manage operation of the display,

wherein the first controller is operatively connected to all payment devices of the user interface configured to receive payment data and is configured to handle all payment data, and wherein the second controller does not handle any sensitive payment data in an unencrypted format.

2. The user interface of claim 1, wherein the first controller determines whether to place the user interface in a secure state based upon receipt of any payment data and whether to provide instructions to the second controller regarding the operation of the display based at least in part on the determination to place the user interface in the secure state.

3. The user interface of claim 1, further comprising at least one sensor operatively connected to the first and second controllers configured to detect separation of the first controller from the second controller, wherein activation of the at least one sensor causes the user interface to become inoperable.

4. The user interface of claim 1, wherein the first controller encrypts a first portion of the payment data according to a host encryption scheme for a host processing system configured to process transactions involving the payment card.

5. The user interface of claim 1, wherein the first controller encrypts a second portion of the payment data according to a local encryption scheme.

6. The user interface of claim 1, wherein the at least one payment device comprises a card reader.

7. The user interface of claim 6, wherein the card reader is a magnetic stripe card reader.