Which IFSF Standards are used where?

Card Scheme Loyalty Engine

Acquirer(s)Front-End

Processor (FEP)

Off-Site

On-Site

Site Controller

Environmental

Monitoring System* Tank Gauge*

IFSF Network - LON or IP

Electronic Payment

Server (EPS)*

LAN Network (IP)

Price Pole Car Wash Code Entry Device Dispenser Dispenser Dispenser

Outdoor Payment Terminal

(OPT)

Key: Device Integration Standard / Payment Standard / Standards applicable to both areas. Note: Equipment marked * may be located on or off site. Other system architectures are also possible.

POS*Card Reader /

Pin Pad

Serial RS-485

Click here for

help

MPPA

Mobile Payment

3-21,

3-60

3-01, 3-26

3-03, 3-11 3-25, 3-273-12, 3-08, 3-11,

3-17, 3-27,

3-10,

3-08,

3-243-043-02

3-21,

3-21,3-21,

3-21,

3-28,

3-29,

3-29

3-29

3-503-50

3-503-50

3-40,

3-40,

3-40

3-403-30,

3-30,

3-05,

3-05,

3-06,

3-06,

3-21,

3-07,

3-16,

2-01, 2-02,

3-01, 3-01,

3-25,

3-26 3-2620180825 v1.0.0

Reference Standard

Part 1-00 Management Introduction

Part 1-01 Glossary

Part 2-01 Communications over Lonworks

Part 2-02 Communications over TCP/IP

Part 2-03 Communications over HTTP REST

Part 3-01 Dispenser Application

Part 3-02 Price Pole Application

Part 3-03 Tank Level Gauge Application

Part 3-04 Car Wash

Part 3-04 Car Wash Overview

Part 3-05 Pin Pad

Part 3-06 Magnetic Card Reader

Part 3-07 Bank Note Acceptor Application

Part 3-08 Printer Application

Part 3-09 Public Network Server Application

Part 3-10 Card Handling Server Application

Part 3-11 Delivery Control Application

Part 3-12 Network Configuration Manager Application

Part 3-13 Human Interface Device

Reference Standard

Part 3-14 Environmental Monitoring Sensor Application

Part 3-15 Line Leak Detector Application

Part 3-16 Customer Operated Payment Terminal (COPT)

Part 3-17 Code Generating Device Application

Part 3-18 POS to FEP Interface

Part 3-19 POS to EPS Interface

Part 3-20 Host to Host Interface

Part 3-21 Security Specifications

Part 3-24 Code Entry Device Application

Part 3-25 Controller Device

Part 3-26 Vapour Recovery Monitoring System Application

Part 3-27 FDC POS Standard Interface

Part 3-28 Standard For Issuing EMV Based Fuel Cards

Part 3-29 Key Management

Part 3-30 POS to EPS V3 Interface

Part 3-40 POS to FEP V2 Interface

Part 3-50 Host to Host V2 Interface

Part 3-60 Mobile Payment to Site Interface

Part 4-01 API Specification Design Rules for JSONPart 4-01 API Specification Design Rules for RAMLPart 4-01 API Specification Implementation GuidelinesPart 4-02 API Specification Core LibrariesPart 4-02 API Specification JSON SchemaPart 4-02 API Specification RAML Core LibrariesPart 4-05 Remote Management and Control API SpecificationPart 4-05 Remote Management and Control Implementation GuidelinesPart 4-10 Fuel Stock Management APIPart 4-15 Pricing API Specification

IFSF Application Programming Interface Specifications and Guidelines

The API Data Dictionary can be accessed here

Welcome to our Standards and supporting documentation. From here you can easily find what you are looking for by clicking on the graphics.

But first click on the ? in the top right hand corner to read what navigation symbols are used and the

common interpretation rules. Its always in the top right hand corner of every page. Click it now.

?

I’M DONE READING

Click here to return to overview

NAVIGATION HELP

Click on the padlock to read about relevant security topics🔐

Click on the magnifying glass to read more about related topic🔎

Click on the spanner to read about Implementation details🔧

Click on the book to read the primary standard📔

Click on the folder to find related standards and other support

material📂

Click on the plug to read the relevant interconnectivity and

network level standards🔌

Click on the memo to find external related standards and

support material📝

Click on the up arrow to navigate one level up.⬆️

Host Computer(s)

Network(s)

Site Computer(s)

🔎

🔎

🔎

?

🔐IFSF Standards define messages betweenapplications. Applications are installedon computers (e.g. on-site or off-site(called host)). The messages can bebetween site applications (such as POS-to-EPS or POS-to-FDC) and between hostapplications (such as HOST-to-HOST).

IFSF applications are installed on one ormore hardware component. The physicallocation of the hardware is determinedby specific implementations.

IFSF application message standards areindependent of the network commslayer. IFSF defines a variety of commsstandards (i.e. Lon, TCP-IP v4, TCP-IP v6,HTTP and HTTPS).

Site Computer(s)

Retail Site Network(s)

🔎

🔎

🔎

?

🔐

IFSF defines messages between siteoperations applications and forecourtequipment.

IFSF defines eight primary site operations applications (Point-of-Service, Controller Device, Unmanned Controller Device, ForecourtDevice Controller, Car Wash Controller, Electronic Payment System,Electronic Loyalty System and Fuel (Wet) Stock Management).

IFSF application message standards aredesigned to enable a variety of sitearchitectures. These include Master-Slave,Client-Server and Peer-to-Peerimplementations, and combinationsof these.

Forecourt Device(s) 🔎

?

Host Graphic under Construction

Please return in a few days for updates.

?

Network Graphic Under Construction

Please return in a few days for updates.

?

• Part 3-21 IFSF Security Specification• Part 3-29 IFSF Key Management Standard

IFSF Security Standards

IFSF Security Standards define HOW IFSF implements globally recognized standards from a variety of differentorganisations (ISO, ASTM, TD). Many of these standards provide multiple ways of achieving the samefunctionality. E.g. they might define AES encryption using 128, 192 or 256 bits. Clearly applications can notinteroperate if one end sends 128 and the other end has implemented 256. IFSF tries to simplify and aidinteroperability by mandating specific settings. You can access relevant security documents by following the linksbelow.

?

IFSF Site Network Standards

IFSF Site Network Standards define the communications layer between applications that both reside on a singlesite. Network standards are given a Part Number beginning with a 2. The communication layer is totallyindependent to the application data. Application data can be carried using any specified communication layer.

• Part 2-01 IFSF Communications over Lonworks standard• This describes the Lonworks network implementation using the FTT Protocol. This extremely reliable

communications protocol was selected due to its ability to operate over existing installed cables no matter what media or cabling topology. Please read EB#1 Cables, Cabling and Cable Connectors.

• Part 2-02 Communications Over TCP IP• IFSF supports both IPv4 and IPv6 addressing. In order for devices to be discovered on the network IFSF

broadcasts device heartbeats on a “Well known port number (3486)” as assigned by IANA. Of course TCP IP can also be used between applications at the same location and remote locations.

• Part 2-03 IFSF Communications Over HTTP REST• IFSF supports both HTTP and HTTPS for RESTful web services. This document describes the

implementation of a web services based communications layer. As with TSP IP applications can reside at the same location or remote.

?

Forecourt Devices Graphic under construction

Please return in a few days for updates.

?

Site Computers Detail Graphic under construction

Please return in a few days for updates.

?

Graphic Page under construction

Please return in a few days for updates.