IFSF Limited Mobile Payment Pay at Pump John

IFSF Limited Mobile Payment Pay at Pump John Carrier, Projects Manager @IFSFonline #IFSFconf2017 W3C Architecture Overview ISO8583Oil P2F MPPA Cloud/WAN Network FEP/ SWITCH CHP PCI Relevant ISO8583Oil Cloud/WAN Network

Mobile Data Network SITES WAN Network Card Acquirer IFSF FDC to POS (Web) Vehicle VISS Console ISO8583Oil H2H Dispenser/ Calculator Smart Phone MP App . MP App

. M-PAY M-PAY Site Computer Chargin g Point 1 IFSF FDC to POS (TCP-IP) POS Terminal Site LAN Sales Application P2H POS Server Card Issuer

Chargin g Point 2 Dispenser/ Calculator FDC Forecourt Network Fuelling Point 1 Fuelling Point 2 NB: These are Logical Components @IFSFonline #IFSFconf2017 W3C Architecture Overview ISO8583Oil P2F MPPA

Cloud/WAN Network FEP/ SWITCH CHP PCI Relevant ISO8583Oil Cloud/WAN Network Mobile Data Network SITES WAN Network W3C #autopa y scope Card Acquirer IFSF FDC to POS (Web)

Vehicle VISS Console ISO8583Oil H2H Dispenser/ Calculator Smart Phone MP App . MP App . M-PAY M-PAY Site Computer Chargin g Point 1

IFSF FDC to POS (TCP-IP) POS Terminal Site LAN Sales Application P2H POS Server Card Issuer Chargin g Point 2 Dispenser/ Calculator FDC Forecourt Network Fuelling Point 1

Fuelling Point 2 NB: These are Logical Components @IFSFonline #IFSFconf2017 W3C Slide Header Walkthrough Architecture Very Important Point - highly simplified diagram For example many missing applications Sites geo-location database interface Site Products database Payments system Sites interface Payment systems Customer account interface Loyalty processing and Electronic Loyalty Servers

Security (Certificates/firewalls/encryption/etc.,) Car parking, Road Tolls, bridges, tunnels and ferries Car valeting (incl. tyre pressure) NB: The above list is incomplete @IFSFonline W3C Slide Header Happy Path Walkthrough Prerequisites - In order to minimise dialogue Fuelling point (i.e. service delivery point) knows where it is Mobile device (Phone, vehicle, tablet) knows where it is Payment (account) available and default known Max fuelling amount pre-set (e.g. $50) All Application WAN and Site LAN networks functioning Fuelling Pump is Idle (nozzle up) and Ready (zero memory) Available and required Product Grades known Loyalty Identifier known and enabled Robotic fuelling and Wireless charging is not yet available Selected Fuelling Point cannot be uniquely identified @IFSFonline W3C Slide Header Happy

Path Walkthrough API Summary - If all goes to plan!! Three Success API Messages Reserve Fuelling Point Approve Fuelling Point (following account authorisation) Completed Fuelling Transaction (the sales and delivery receipt) Two Failure API Messages Free Fuelling Point Cancel Fuelling Transaction (following account authorisation) @IFSFonline W3C SlidePath Sad Header Walkthrough API Summary - When something goes wrong >95% of transactions follow happy path but. The sad path can be hugely problematic and difficult to fix At least 22 Sad paths identified and need thorough testing Two Failure API Messages Cancel Fuelling Point (to Un-authorise a pre-authorised account payment) Free Fuelling Point (to un-reserve a Fuelling point after a User, Systems or operator intervention/error) And many timers required esp. related to connectivity and user operational issues

E.g. no Failure message from site No Approve message to site How long do you wait??? What length of time for a timer? Nozzle juggling , mixed service mode complexities (post pay and OPTs at same time) @IFSFonline W3C Slide Header Alternative Scenarios Conditions and Exceptions Conditional Processing Digital Offers redemption (changes unit price or final sale price) Payment account not pre-configured (dynamically selected/entered) Acceptable product grade(s) not configured Location services not enabled Service Point needs to be uniquely identified First use (Fire and other safety regulations to be followed) Local paper receipt required (Trading standards)

Exceptions Hardware and mechanical failures (including network WAN and LAN) Pump not free, Pump out of order, pump configured wrong Insufficient funds in account or account not available Operator, cashier, customer, vehicle or system aborts transaction Incompatible product / grade selected @IFSFonline W3C Slide Misc. Header Operational Issues Operational issues Mixed Service Modes Cashier needs to know status of the Mobile Payment transaction at all times to reduce accidental drive offs (Fuel is taken but not paid for) Fuelling Point must handle nozzle juggling (if not robotic or wireless) Acceptable product grade(s) not configured Fuelling point dynamically (i.e. per transaction) sets unit price and service mode) Alternative Architectures IFSF has identified 5 real-world working architectures this one is winning

because Site doesnt require OPT, CRIND or COPT but does need unmanned controller device No PCI re-certification of site EPS (or any other connected components) is necessary No PCI relevant data (neither sensitive or personal or private) is required to be transmitted to site Often referred to as OTA (over the air authorisation) No OIML nor W&M recertification of site equipment / operations needed @IFSFonline W3C Shell Fill & Go Happy Path Slide Header @IFSFonline W3C Slide Shell Header Fill & Go Happy Path @IFSFonline @IFSFonline W3C Slide Shell Header Fill & Go Happy Path

@IFSFonline W3C Slide Shell Header Fill & Go Happy Path @IFSFonline W3C Slide Shell Header Fill & Go Happy Path @IFSFonline W3C