(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2014/0074714 A1
`(43) Pub. Date:
`Mar. 13, 2014
`MELONE et al.
`
`US 20140074714A1
`
`(54)
`
`(71)
`(72)
`
`(21)
`(22)
`
`(60)
`
`ATTENDED DISPENSING ENVIRONMENT
`UTILIZING MOBILE PAYMENT
`
`Applicant: Gilbarco S.r.l., Firenze (IT)
`
`Inventors: Cristian MELONE, Prato (IT):
`Giovanni CARAPELLI, High Point,
`NC (US)
`Appl. No.: 14/020, 181
`Filed:
`Sep. 6, 2013
`
`Related U.S. Application Data
`Provisional application No. 61/698.912, filed on Sep.
`10, 2012.
`
`Publication Classification
`
`(51)
`
`Int. C.
`G06O20/32
`
`(2006.01)
`
`(52) U.S. Cl.
`CPC ............ G06O20/322 (2013.01); G06O20/327
`(2013.01); G06O20/3274 (2013.01); G06Q
`20/3278 (2013.01)
`USPC ............. 705/44; 235/381; 235/494; 235/493;
`235/487; 705/39
`
`ABSTRACT
`(57)
`A payment system is provided for attended vending machines
`allowing customers to initiate mobile payment for goods or
`services with an attendant handheld. The handheld can gen
`erate a transaction identifier based on obtained transaction
`information related to goods or services dispensed, which can
`be provided to a mobile payment server. The handheld can
`render a representation of the transaction identifier for con
`Sumption by a mobile device, such as a quick response (QR)
`code, bar code, near field communication (NFC) field, Blue
`tooth communication, etc. The mobile device can process the
`representation to obtain the transaction identifier for initiating
`payment with the mobile payment server.
`
`/ 3:
`
`
`
`3: E PAYEN SERVER
`
`THE
`
`PARTY SERVER
`
`TRANSACTN
`NFRAT:BN
`CyNE
`
`ABRYASN
`EERWNNG
`CyPNEN"
`
`SANSASN
`RESSENG CityNEN"
`
`NETWRK
`CyNCAN,
`CyPNEN"
`
`NERFACE CONENT
`
`AUTHORNG
`CyNEN
`
`ARAETER
`ANAYNG
`CVPNEN
`
`YET/RK
`:C:OWN AN
`CPNEN
`
`Petitioner Kiosoft Exhibit 1005
`1
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 1 of 9
`
`US 2014/0074714 A1
`
`/
`
`{{
`
`R ARY
`SERWER
`
`NTERNE BR WN
`
`
`
`2
`
`4:
`
`
`
`BE
`AYMENT
`SERVER
`
`
`
`BEWE
`s
`
`CD is
`
`STES
`
`8
`
`2.
`
`
`
`ENET RK
`
`FG.
`
`RETA ii. SITE
`104
`--4-
`
`8
`
`AA/
`| FCC
`- - - - 1
`
`\
`106)
`
`A
`
`1. - - - - -
`i24 N 2
`
`Petitioner Kiosoft Exhibit 1005
`2
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 2 of 9
`
`US 2014/0074714 A1
`
`
`
`AE
`
`:
`
`E. EWCE
`
`NTERFA CE {{WPNENT
`
`NTERFACE COMNENT
`
`RANSASY
`NRAON
`{{NENT
`
`REESENAN
`CONSUIN COWBOY ENT
`
`TRANSACTN
`BEN FER GENERATING
`CNEN
`
`RANSACON
`ENT FEER OSTANN
`CyN EN
`
`RERESENABN
`RENERN, CVONENT
`
`PAYWENT ENTAN
`CyPNENT
`
`WENN: A CNE
`CyNCANG
`CNEN
`
`YE WEBRK
`CYNCANG
`CPNENT
`
`NEWERK
`CW. J N CANG
`CyN EN
`
`FG, 2.
`
`Petitioner Kiosoft Exhibit 1005
`3
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 3 of 9
`
`US 2014/0074714 A1
`
`/ 3.
`
`
`
`83 EATENT SERVER
`
`TER ARY SERVER
`
`TRANSACTN
`NFORAN
`CyNEY
`
`A RAN
`EERENENG
`CNEN
`
`TRANSA83.
`RESSENG CNEN
`
`NETWRK
`CWNSATNG
`CONEN
`
`NERFACE CMPONSENT
`
`AURYN
`C, CNEN
`
`PARAEER
`ANAEYNG
`sy FNENT
`
`NE". R.
`C{WJNAN
`scNEN
`
`F.G. 3
`
`Petitioner Kiosoft Exhibit 1005
`4
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 4 of 9
`
`US 2014/0074714 A1
`
`/ 48
`
`:
`
`48.
`
`START
`
`BAN NFRABN RE:GARNGA
`RANSA TNA A WENN. ACH NE
`
`GENERATE A, TRANSACTION BEY FEER
`SASE N ART N THE INFOBRA
`REGARY &
`E RANSACTEN
`
`- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
`RAYS.T E RANSACTN ENT FER :- 48
`ANf3 NFORMATEN ' A BE
`AYEY SERVER
`
`E.
`RENER A RERESENTACBN OBF
`RANSACTN ENT FEER CNSJVABLE BY
`E BE EWCE
`
`48
`
`- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
`RECEWE. A. PAYEN CONFERA3
`CE
`N. ON
`{}N {} - to
`REECEON FRV HE WEBEAY WEEN"
`SERVER FOR TE ANSACTN
`
`
`
`
`
`
`
`F.G. &
`
`Petitioner Kiosoft Exhibit 1005
`5
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 5 of 9
`
`US 2014/0074714 A1
`
`STAR
`
`{} A' A RERESENTA BN 8: A
`"RANSAC BN BEN FER FV AN
`AENANT ANEED A A WEN: N.
`WACNE
`
`S.
`
`ECE E RANSACTN ENTFER
`FR
`E REPRESENTAN
`
`NTAE PAYMENT FER A RANSACT ON BY
`Cyy NAN E RANSACTN
`ENT FER
`A y{83. AYMENT SERVER
`
`---------------------------------
`RE.8 EVE A SAY ENT CNRATN BR
`REECBN FR8y
`E WOBSE AY ENT
`SERVER FREE RANSACTSN
`
`
`
`S.
`
`SS
`
`F.G. S.
`
`Petitioner Kiosoft Exhibit 1005
`6
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 6 of 9
`
`US 2014/0074714 A1
`
`/ { }}
`
`START
`
`
`
`(STAN EN FORWAN F A RANSACN
`RELATING O. A 3E BEVE FROW A
`ANDE A' A REA STE
`
`EERNE AT THE WOSE DEVCE
`REQUIRES TRD PARTY AUTORIZATION
`
`CNCAEWT: A
`SERVER 8 A.H. R.E. T.
`FOR THE TRANSACTION
`
`R PARTY
`E.
`E.V. CE
`
`PRCESS PAYVEN FREE RANSA CON
`BASE} N
`E NF8&AN AND SE
`ARATN OBy
`E.
`& AY
`SERVER
`
`2
`
`s:
`
`{{
`
`{{88
`
`EN
`
`FG. 6
`
`Petitioner Kiosoft Exhibit 1005
`7
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 7 of 9
`
`US 2014/0074714 A1
`
`4.
`
`78
`
`8.
`EV CE
`
`WENN,
`YACH NE
`
`PAYENT
`SERVER
`
`ARE
`SPENSNG 1.
`
`t
`
`SENSE
`
`SPENSN
`CMETE
`
`NFO REQUEST
`
`
`
`
`
`
`
`
`
`
`
`
`
`74:
`
`6
`
`8
`
`fi
`
`NF RESENSE
`1
`
`GENERAE RANSA8
`ENT FER AN
`RERESENASON
`
`TRANSACN NF
`
`7
`
`TAN
`REPRESENTAN 23
`
`NTATE BAYENT
`
`T26
`
`
`
`
`
`
`
`PAYMEN CNRM?, EC
`
`Petitioner Kiosoft Exhibit 1005
`8
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 8 of 9
`
`US 2014/0074714 A1
`
`
`
`/ S.
`
`PROCESSNs
`UN'S
`
`SYSTEV
`MENRY
`
`yASS
`STOBRAGE
`
`NERFACE
`CyPCNENTS
`
`FG. 8
`
`Petitioner Kiosoft Exhibit 1005
`9
`
`

`

`Patent Application Publication
`
`Mar. 13, 2014 Sheet 9 of 9
`
`US 2014/0074714 A1
`
`/ 9:
`
`$3.
`
`SERVERS)
`
`SERVER
`AA
`STORES
`
`
`
`{
`
`C ENS)
`
`CLEN
`AA
`STORES
`
`
`
`
`
`
`
`
`
`
`
`CVM N AN
`FRAMEWORK
`
`FG.
`
`Petitioner Kiosoft Exhibit 1005
`10
`
`

`

`US 2014/0074714 A1
`
`Mar. 13, 2014
`
`ATTENDED DISPENSING ENVIRONMENT
`UTILIZING MOBILE PAYMENT
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`0001. The present application claims the benefit of U.S.
`patent application No. 61/698.912, filed Sep. 10, 2012, and
`entitled ATTENDED DISPENSING ENVIRONMENT
`UTILIZING MOBILE PAYMENT, the disclosure of which
`is hereby incorporated by reference as if set forth verbatim
`herein in its entirety and relied upon for all purposes.
`
`TECHNICAL FIELD
`0002 The subject matter described herein relates gener
`ally to a fueling environment or other attended vending envi
`ronment where goods or services are dispensed. More par
`ticularly, subject matter described herein relates to use of a
`mobile phone or other portable device to effect payment for
`an attended vending transaction.
`
`BACKGROUND
`0003 Transaction processing within a retail attended fuel
`ing environment conventionally includes interaction between
`a customer and an attendant operating a fuel dispenser. In
`Such environments, after fuel is dispensed to a customer, the
`attendant requests apost-payment from the customer. In some
`examples, the attendant can carry a handheld controller to
`process credit card or other payment methods from the cus
`tomer based on information regarding the fuel dispensing
`transaction. The fuel dispenser can provide the information to
`the handheld electronically by way of a forecourt controller.
`Such controllers are communicatively coupled to one or more
`fuel dispensers and other devices. Such as the attendants
`handheld, a point-of-sale (POS) terminal, etc., and/or can
`connect to one or more banks (e.g., a payment server thereof)
`to process post-payment from a customer.
`0004. The forecourt controller typically connects to the
`handhelds via a wireless connection, such as WiFi connection
`to an associated local area network (LAN) and/or a Bluetooth
`connection. In addition, the forecourt controller connects to
`the fuel dispensers via local wiring and to payment servers,
`loyalty servers, and/or other remote devices via a network
`such as the Internet. Thus, for example, the forecourt control
`ler can provide information regarding the fuel dispensing of a
`customer to the handheld of an attendant. The handheld pro
`cesses payment from the customer by reading a credit card or
`otherform of payment and transmitting the information to the
`forecourt controller. The forecourt controller accordingly
`communicates payment information for authorization to the
`payment server, and approves or rejects the transaction, an
`indication of which is received by the forecourt controller and
`transmitted to the handheld.
`0005 Various aspects of vending machine systems using
`mobile devices are disclosed in U.S. Pat. Nos. 8,032,414,
`7,574,377, and 7,664.885, incorporated herein by reference
`for all purposes.
`
`SUMMARY
`0006. The following presents a simplified summary of one
`or more aspects of the Subject matter disclosed herein to
`provide a basic understanding thereof. This Summary is not
`an extensive overview of all contemplated aspects, and is
`intended to neither identify key or critical elements of all
`
`aspects nor delineate the scope of any or all aspects. Its sole
`purpose is to present some concepts of one or more aspects in
`a simplified form as a prelude to the more detailed description
`that follows.
`0007 Various aspects described herein are directed to pro
`cessing a payment at an attended vending machine, Such as a
`fuel dispenser at a service station. Attendants at the retail site
`can operate handhelds for communicating with the vending
`machines (e.g., fuel dispensers) to process payment for dis
`pensing goods or services, and the handhelds can effectuate
`payment via mobile devices. In this regard, a handheld can
`generate a transaction identifier allowing a mobile device to
`process the transaction identifier to complete payment at the
`handheld. In one example, the handheld generates a represen
`tation of the transaction identifier consumable by the mobile
`device from the handheld, another device participating with
`the vending machine in a network, a printout from Such
`devices, and/or the like. The attendant can initiate this pro
`cess, in one example.
`0008 For example, the generated representation can be a
`visual representation, such as a quick response (QR) code, bar
`code, a numeric identifier, etc. In another example, the gen
`erated representation can include a short-range communica
`tion representation, such as a near field communication
`(NFC) field, a Bluetooth transmission, etc. In either case, the
`mobile device consumes the transaction identifier by scan
`ning the printed representation, receiving the short-range
`communication, etc. The mobile device can then acquire the
`transaction identifier from the representation, and can send
`the transaction identifier, or information indicated in the
`transaction identifier, to a remote server to process the mobile
`payment. The information can include the transaction identi
`fier or other details of the transaction, such as the vendor,
`purchase amount, etc. The remote server processes payment
`based on the information, and can provide a status for the
`payment processing to the mobile device and/or the handheld.
`0009. To the accomplishment of the foregoing and related
`ends, the one or more aspects comprise the features herein
`after fully described and particularly pointed out in the
`claims. The following description and the annexed drawings
`set forth in detail certain illustrative features of the one or
`more aspects. These features are indicative, however, of but a
`few of the various ways in which the principles of various
`aspects may be employed, and this description is intended to
`include all such aspects and their equivalents.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`0010. The disclosed aspects will hereinafter be described
`in conjunction with the appended drawings, provided to illus
`trate and not to limit the disclosed aspects, wherein like
`designations may denote like elements, and in which:
`0011
`FIG. 1 is a diagrammatic representation of an aspect
`of an example system for processing transactions at an
`attended vending machine.
`0012 FIG. 2 is an aspect of an example system for com
`municating transaction information between a handheld and a
`mobile device.
`0013 FIG. 3 is an aspect of an example system for pro
`cessing mobile payment with third party authorization.
`0014 FIG. 4 is an aspect of an example methodology for
`providing a transaction identifier representation to a mobile
`device for initiating mobile payment for the transaction.
`
`Petitioner Kiosoft Exhibit 1005
`11
`
`

`

`US 2014/0074714 A1
`
`Mar. 13, 2014
`
`0015 FIG. 5 is an aspect of an example methodology for
`initiating mobile payment for a transaction at an attended
`vending machine.
`0016 FIG. 6 is an aspect of an example methodology for
`processing mobile payment with third party authorization.
`0017 FIG. 7 is a diagrammatic representation showing
`operational aspects of a system for initiating mobile pay
`ments of transactions at attended vending machines.
`0018 FIG. 8 is an aspect of an example system in accor
`dance with aspects described herein.
`0019 FIG. 9 is an aspect of an example communication
`environment in accordance with aspects described herein.
`
`DETAILED DESCRIPTION
`0020 Reference will now be made in detail to various
`aspects, one or more examples of which are illustrated in the
`accompanying drawings. Each example is provided by way of
`explanation, and not limitation of the aspects. In fact, it will be
`apparent to those skilled in the art that modifications and
`variations can be made in the described aspects without
`departing from the scope or spirit thereof. For instance, fea
`tures illustrated or described as part of one example may be
`used on another example to yield a still further example. Thus,
`it is intended that the described aspects cover such modifica
`tions and variations as come within the scope of the appended
`claims and their equivalents.
`0021
`Described herein are various aspects relating to pro
`viding payment processing at an attended vending machine
`by allowing an attendant handheld to produce a representa
`tion of transaction information that is consumable by a con
`Sumer's mobile device, such as a “smart phone' or tablet
`computer. The mobile device can thus obtain the transaction
`information and can initiate a mobile payment for goods or
`services dispensed at the vending machine based on the trans
`action identifier. The representation produced by the atten
`dant handheld can include one or more visual representations
`(e.g., a quick response (QR) code, a bar code, a transaction
`number, etc.), one or more communicative representations
`(e.g., a NFC field, radio frequency identifier (RFID) field, a
`Bluetooth transmission, etc.), and/or the like.
`0022. As used in this application, the terms “component.”
`“module.” “system’’ and the like are intended to include a
`computer-related entity, such as but not limited to hardware,
`firmware, a combination of hardware and Software, Software,
`or Software in execution. For example, a component may be,
`but is not limited to being, a process running on a processor,
`a processor, an object, an executable, a thread of execution, a
`program, and/or a computer. By way of illustration, both an
`application running on a computing device and the comput
`ing device can be a component. One or more components can
`reside within a process and/or thread of execution and a
`component may be localized on one computer and/or distrib
`uted between two or more computers. In addition, these com
`ponents can execute from various computer readable media
`having various data structures stored thereon. The compo
`nents may communicate by way of local and/or remote pro
`cesses such as in accordance with a signal having one or more
`data packets, such as data from one component interacting
`with another component in a local system, distributed system,
`and/or across a network Such as the Internet with other sys
`tems by way of the signal.
`0023 Artificial intelligence based systems (e.g., explicitly
`and/or implicitly trained classifiers) can be employed in con
`nection with performing inference and/or probabilistic deter
`
`minations and/or statistical-based determinations in accor
`dance with one or more aspects of the Subject matter as
`described hereinafter. As used herein, the term “inference'
`refers generally to the process of reasoning about or inferring
`states of the system, environment, and/or user from a set of
`observations as captured via events and/or data. Inference can
`be employed to identify a specific context or action, or can
`generate a probability distribution over states, for example.
`The inference can be probabilistic—that is, the computation
`of a probability distribution over states of interest based on a
`consideration of data and events. Inference can also refer to
`techniques employed for generating higher-level events from
`a set of events and/or data. Such inference results in the
`construction of new events or actions from a set of observed
`events or stored event data, regardless of whether the events
`are correlated in close temporal proximity, and whether the
`events and data come from one or several event and data
`Sources. Various classification schemes and/or systems (e.g.,
`Support vector machines, neural networks, expert systems,
`Bayesian belief networks, fuZZy logic, data fusion engines,
`etc.), for example, can be employed in connection with per
`forming automatic and/or inferred actions in connection with
`the subject matter.
`0024. Furthermore, the subject matter can be implemented
`as a method, apparatus, or article of manufacture using stan
`dard programming and/or engineering techniques to produce
`software, firmware, hardware, or any combination thereof to
`control a computer to implement the disclosed Subject matter.
`The term “article of manufacture' as used herein is intended
`to encompass a computer program accessible from any com
`puter-readable device, carrier, or media. For example, com
`puter readable media can include but are not limited to mag
`netic storage devices (e.g., hard disk, floppy disk, magnetic
`strips . . . ), optical disks (e.g., compact disk (CD), digital
`versatile disk (DVD) . . . ), smart cards, and flash memory
`devices (e.g., card, Stick, key drive...). Additionally it is to
`be appreciated that a carrier wave can be employed to carry
`computer-readable electronic data Such as those used in trans
`mitting and receiving electronic mail or in accessing a net
`work such as the Internet or a local area network (LAN). Of
`course, those skilled in the art will recognize many modifi
`cations can be made to this configuration without departing
`from the scope or spirit of the subject matter.
`0025. Moreover, the term or is intended to mean an inclu
`sive or rather than an exclusive “or.” That is, unless specified
`otherwise, or clear from the context, the phrase “X employs A
`or B is intended to mean any of the natural inclusive permu
`tations. That is, the phrase “X employs A or B is satisfied by
`any of the following instances: Xemploys A, Xemploys B; or
`X employs both A and B. In addition, the articles “a” and an
`as used in this application and the appended claims should
`generally be construed to mean one or more unless specified
`otherwise or clear from the context to be directed to a singular
`form.
`0026 Various aspects or features will be presented in
`terms of systems that may include a number of devices, com
`ponents, modules, and the like. It is to be understood and
`appreciated that the various systems may include additional
`devices, components, modules, etc. and/or may not include
`all of the devices, components, modules etc. discussed in
`connection with the figures. A combination of these
`approaches may also be used.
`0027 FIG. 1 illustrates an example system 100 for pro
`cessing mobile payments in a vending environment. System
`
`Petitioner Kiosoft Exhibit 1005
`12
`
`

`

`US 2014/0074714 A1
`
`Mar. 13, 2014
`
`100 includes one or more retail sites 102, which can each
`include one or more vending machines 104 (such as a fuel
`dispenser) and one or more handhelds 106 for processing
`payment information. In the case of a fueling environment,
`for example, retail site 102 typically includes a forecourt
`controller (FCC) 108 for facilitating communication between
`vending machine 104 and handheld 106 or other components
`at the retail site. In one example, WiFi 110, which can repre
`sent an access point, network Switch, router, and/or various
`other devices to implement a WiFi network, can be used by
`FCC 108 and handheld 106 to facilitate communication ther
`ebetween. In addition, WiFi 110 can provide a wired or wire
`less connection from retail site 102 to Internet or virtual
`private network (VPN) 112 for communicating with addi
`tional devices. Handheld 106 can additionally or alternatively
`communicate with vending machine 104 directly via a wire
`less connection (e.g., WiFi, Bluetooth, ZigBee, etc.). In addi
`tional examples, the handheld 106 can be a mobile device (or
`can include a mobile radio) that communicates with retail site
`102 (and vending machine 104) via mobile network 126,
`Internet 112, etc. Moreover, one or more mobile devices 124
`carried by or otherwise associated with a customer can be
`presentat retail site 102. The mobile device(s) 124, which, for
`example, may be a customer's Smart phone or tablet com
`puter, can communicate with Internet 112 via a mobile net
`work 126 and/or WiFi 110.
`0028 System 100 also includes a mobile payment server
`114 for processing payments initiated by mobile device 124.
`The mobile payment server 114 can communicate with (and/
`or provide) multiple databases that store transaction data,
`such as a device identifier database 116 that stores informa
`tion regarding a plurality of mobile devices, a users database
`118, that stores information regarding mobile device users
`registered to initiate mobile payments via a mobile device, a
`sites database 120 that stores information regarding the retail
`site(s) 102 (e.g., a site identifier, Vending machine identifiers,
`merchant bank information, etc.), and/or other databases.
`Components of system 100 can communicate with a bank122
`or one or more components thereof. Such as a payment server,
`as well as one or more loyalty servers hosted by the operator
`of the retail site or a third party host, such as a third party
`Server 130.
`0029. In an example, retail site(s) 102 can generate trans
`action information based on goods or services dispensed by
`vending machine 104. Such as transaction amount, goods or
`services dispensed, a transaction identifier, and can Submit
`the transaction information to mobile payment server 114 via
`internet or VPN 112. In this regard, a mobile device 124 can
`initiate payment at the retail site 102, and can communicate
`with mobile payment server 114 to complete the transaction
`based on the information received from retail site 102 as well.
`0030 Vending machine 104 can dispense goods or ser
`vices to a customer. The vending machine 104 can be attended
`such that an attendant handheld 106 is utilized to authorize
`operation of the vending machine 104 and to facilitate pay
`ment for the goods or services. In one example, the vending
`machine can be a full service fuel dispenser at a service
`station attended by one or more attendants that can utilize
`handheld 106 for communicating with a fuel dispenser as
`described. The attendant can authorize dispensing at the fuel
`dispenser via handheld 106 by communicating with the fuel
`dispenser. In one example, handheld 106 can provide an
`interface allowing selection of the desired fuel dispenser from
`among several to authorize dispensing for a given customer.
`
`This can initiate a dispensing process for which payment can
`be subsequently processed as well. Selection of the fuel dis
`penser by handheld 106 can be effectuated manually, by
`scanning or otherwise inputting a code displayed on the fuel
`dispenser, by reading a proximity identifier, Such as NFC,
`RFID, etc., and/or the like.
`0031. Thus, the attendant (not shown) can cause the hand
`held 106 to obtain information regarding the dispensing (e.g.,
`once the fuel dispenser is authorized to dispense), and to
`generate transaction information for processing payment.
`The transaction information can include a cost (e.g., a fixed
`cost or a number of units dispensed along with cost per unit),
`sales tax information, and/or other information for use in
`processing payment. In one example, the handheld 106 can
`allow the attendant to manually enter at least a portion of the
`transaction information (e.g., where the fuel dispenser is not
`equipped to communicate such to the handheld 106). The
`handheld 106 can also generate a transaction identifier for
`associating with the transaction. The transaction identifier
`can be unique for the transaction (e.g., for the vending
`machine 104, retail site 102, and customer accessing Such),
`unique to the vending machine 104 within retail site 102.
`and/or the like.
`0032. In one example, handheld 106 can cause the trans
`action information to be delivered from the retail site 102 to
`the mobile payment server 114 for Subsequently processing
`mobile payment from a mobile device 124. In this regard,
`handheld 106 can utilize WiFi 110 connection to the Internet
`or VPN 112 to communicate the information to the mobile
`payment server 114. In other examples, handheld 106 can
`communicate the information through other devices at the
`service station, such as a separate point-of-sale (POS) termi
`nal (not shown) that communicates with handheld 106 via
`FCC 108 or other wired or wireless connections, and also
`communicates with Internet or VPN 112. In yet other
`examples, the transaction identifier can identify the retail site
`102, vending machine 104, and/or other information that the
`mobile payment server 114 can use to obtain remaining trans
`action information from the retail site 102, vending machine
`104, etc. once engaged by mobile device 124 for initiating
`payment. For example, the mobile device 124 can include the
`transaction identifier in a payment initiation request to the
`mobile payment server 114.
`0033. The mobile payment server 114 can receive a pay
`ment initiation request from mobile device 124, and can pro
`cess the payment based on correlating a transaction identifier
`with a retail site 102 and/or a related vending machine 104. In
`one example, this can include correlating the transaction
`identifier received from mobile device 124 with a transaction
`identifier previously received from the vending machine 104
`or handheld 106 operating the vending machine (e.g., via
`WiFi at the retail site 102 over Internet 102). The mobile
`payment server 114 can accordingly determine transaction
`information based on obtaining transaction information
`received with the matching transaction identifier from the
`vending machine 104 or handheld 106. In another example,
`where the transaction identifier received from mobile device
`124 identifies the vending machine 104, mobile payment
`server 114 can request the transaction information from the
`identified vending machine 104. In either case, mobile pay
`ment server 114 can communicate with bank 122 to approve
`payment for the transaction. In one example, mobile payment
`server 114 can communicate a confirmation or rejection for
`the transaction to vending machine 104 via Internet or VPN
`
`Petitioner Kiosoft Exhibit 1005
`13
`
`

`

`US 2014/0074714 A1
`
`Mar. 13, 2014
`
`112, which can be forwarded to handheld 106 or other devices
`at the retail site 102 via WiFi 110.
`0034. In another example, a third party server 130 can be
`employed to provide another layer of authorization for a
`mobile payment. In this example, mobile payment server 114
`can obtain instructions to contact third party server 130 for
`payments initiated by certain mobile devices. The instruc
`tions can be tied to the mobile device identifier stored by
`mobile payment server 114 (e.g., IDs in device IDs database
`116), or otherwise specified by handheld 106 based on infor
`mation received during transaction or payment processing,
`Such as a mobile device identifier, a mobile device type, an
`indication from the mobile device upon obtaining the trans
`action identifier (e.g., a credit card or credit card type used
`during transaction processing), etc. In any case, mobile pay
`ment server 114 can provide transaction information to the
`third party server 130 based on related instructions, and the
`third party server 130 can approve or deny the transaction, or
`provide additional information, such as a payment limit,
`approval expiration time, etc.
`0035. In this example, third party server 130 can be a
`corporate server that allows for manual approval/denial of
`transactions on company mobile devices 124 or mobile
`devices initiating payments using company credit cards. The
`manual approval can include presenting transaction informa
`tion from the third party server 130 to an interface or other
`devices with which the server 130 can communicate, such as
`one or more computers on a LAN, one or more mobile devices
`via Internet 112 and mobile network 126, etc. In other
`examples, the third party server 130 can allow for parental
`approval of transactions from their children's mobile devices.
`For example, third party server 130 can push transaction
`information to a parental mobile device for approval/denial.
`0036. In other examples, the third party server 130 can
`also allow programs to interface therewith for automated
`approval/denial of transactions. For example, a program on a
`corporate server can receive transaction information from
`third party server 130, and can approve or deny the transac
`tion based on additional factors, such as time of day, day of
`week, location of retail site 102 or mobile device 124, etc., to
`validate the transaction according to one or more corporate
`policies. In addition, mobile payment server 114 can contact
`the third party server 130 for approval as part of a prepayment
`and/or post-payment process, as described. In one example,
`though retail site 102 may typically use post-payment pro
`cessing, handheld 106 can present the option for a pre-autho
`rization with third party server 130 before vending machine
`104 dispensing. In this example, mobile device 124 can com
`municate information regarding pre-authorization to hand
`held 106 (e.g., via QR code, bar code, NFC field, Bluetooth,
`etc.), and handheld 106 can pre-authorize mobile device 124
`for the transaction (e.g., via mobile payment server 114 com
`municating with third party server 130 or third party server
`130 directly). In one example, third party server 130 can
`communicate a pre-approval maximum amount for the trans
`action back to handheld 106 or mobile payment server 114.
`0037. In one example, to facilitate mobile payment initia
`tion at mobile device 124, handheld 106 and/or FCC 108 can
`provide the transaction identifier to a mobile device, such as
`mobile device 124, in a consumable format. For example,
`handheld 106 can generate a readable representation of the
`transaction identifier, Such as a QR code, bar code, numeric
`identifier, and/or the like. In another example, handheld 106
`can generate a communicative representation of the transac
`
`tion identifier, such as a NFC field, Bluetooth or other wire
`less transmission, etc. In any case, the mobile device 124 can
`obtain and process the representation, as described further
`herein, and can accordingly initiate mobile payment based on
`a related transaction identifier.
`0038. In a further example, handheld 106 and mobile
`device 124 can establish a wireless connection (e.g., over
`which handheld 106 can transmit the communicative repre
`sentation of the transaction identifier). For example, the wire
`less communication can include a NFC connection via an
`NFC field, a Bluetooth connection, etc. In this example,
`mobile device 124 can communicate with mobile payment
`server 114 over the wireless connection with handheld 106 so
`as not to use resource of the mobile device 124 for such
`communication. This can be beneficial to a user of the mobile
`device 124, as can mobile device 124 communicating with
`WiFi 110 as described, because many mobile service provid
`ers limit bandwidth for communicating over mobile network
`126. In this example, mobile device 124 transmits data related
`to initiating mobile payment, as described, which traverses
`handheld 106 to reach Internet or VPN 112 and on to mobile
`payment server 114; this can include handheld 106 traversing
`WiFi 110 or other Internet connections at retail site 102.
`0039. In an example, handheld 106 can include the mobile
`payment server 114 functionality to mitigate the need for a
`separate server and related communication. Thus, han