Method and apparatus for mobile payment transactions with product dispensers

Abstract

A method and apparatus for mobile payment transactions with a product dispenser. Various exemplary methods and devices are provided for electronically communicating with a product dispenser of a mobile device. Generally, a mobile device may request a secure connection with a product dispenser detected in proximity to the mobile device. The mobile device may transmit request data to a network cloud server to authorize a mobile payment application executing on the mobile device, and may receive response data from the network cloud server indicating that the payment application has been authorized to process a payment for a product dispensable from the product dispenser. Both the mobile device and the product dispenser establish a secure connection using the security key included in the response data regardless of whether the product dispenser has established a connection with the network cloud server.

Description

[0001] Related Applications

[0002] This application claims priority under 35 U.S.C. § 119(e) to U.S. Patent Application No. 15 / 888,663, filed on Feb. 5, 2018, the entire content of which is hereby expressly incorporated by reference herein. Technical Field

[0003] The present disclosure generally relates to methods and apparatus for electronic communication of a product dispenser, and more particularly to payment transactions for products dispensable from a product dispenser performed via a mobile device. Background Art

[0004] There are various product dispensers that can dispense products. For example, the retail petroleum industry utilizes various types of fuel dispensers to dispense fuel to customers. Some form of remote dispenser controller has traditionally been used to control the actual dispensing of fuel by the fuel dispenser. The dispenser controller is typically co-located with the fuel dispenser and coupled to a store interface unit such that a site attendant can monitor and control a particular fueling dispenser from a building at the site (e.g., a gas station or other store). The dispenser controller sends data signals to the fuel dispenser, providing it with various information and commands. The information has traditionally included price, a preset amount of fuel to be dispensed, and authorization to dispense fuel. The fuel dispenser also sends data signals to the dispenser controller, traditionally including pump number, pump status, volume of fuel dispensed, and sale price.

[0005] Point-of-sale (POS) systems, such as in-store POS terminals or payment modules embedded in fuel dispensers, have traditionally been used to control the payment functionality of fuel dispensers. The POS system is often co-located with the fuel dispenser and sends data signals to the fuel dispenser, providing it with various information and commands. The information has traditionally included prompting control, graphics, and media for display on a display screen of the fuel dispenser. The fuel dispenser also sends data signals to the POS system, traditionally including pump number, prompt status, transaction data, and sale price.

[0006] As mobile payments become more and more common, POS systems can accept mobile payments for fuel and other goods / services. Conventionally, to authorize a mobile payment transaction, a fuel dispenser communicates with a POS system to complete a fuel purchase transaction. The POS system can operate as an intermediary between the fuel dispenser and a remote source such as a network cloud, hosting a network cloud fuel management service. However, the existing infrastructure for using mobile payments at a POS system (e.g., at a fuel supply service station) is cumbersome, making it generally inconvenient for customers to perform payments at the POS system for fuel and other goods / services. Additionally, although many customers prefer to stay outside during fuel supply to be able to use their mobile devices to pay for the transaction, customers are required to enter a store (e.g., a fuel supply service station) to complete the fuel purchase transaction.

[0007] Alternatively, the fuel dispenser can be enabled to communicate directly with the network cloud to authorize mobile payments. Whether the fuel dispenser communicates directly with the network cloud or via a field dispenser controller (e.g., a POS system) communicatively coupled to the dispenser with the network cloud, the network cloud is required to transmit mobile payment authorization information to the fuel dispensing site, such as directly to the dispenser or to the dispenser controller. Since inbound traffic must be allowed access to the fuel dispensing site, this creates a security risk, exposing security data (e.g., payment details, customer personal identification number (PIN), etc.) to potential fraudulent access. Also, continuous connectivity between the network cloud and the fuel dispenser and / or POS system is required for performing fuel purchase transactions. Additionally, typically only certain types of payments are accepted via the POS system, which limits the payment options available to customers.

[0008] Accordingly, there is still a need for improved methods and devices for electronic communication of fuel dispensers to perform payment transactions. SUMMARY OF THE INVENTION

[0009] Generally, methods and devices for electronic communication of product dispensers are provided. In particular, methods and devices for performing payment transactions for products that can be dispensed from a product dispenser via a mobile device are provided.

[0010] In one aspect, a mobile device is provided that, in one embodiment, includes a communication mechanism and a processor. The communication mechanism is configured to detect a product dispenser in the vicinity of the mobile device. The processor is configured to transmit, via the communication mechanism, a request to establish a secure connection with the product dispenser. The processor is configured to transmit request data via a wireless connection to a network cloud server, the request data requesting authorization of a payment application of the mobile device, and the processor is further configured to receive, via the wireless connection, response data from the network cloud server, the response data indicating that the payment application has been authorized to process payments for products that can be dispensed from the product dispenser.

[0011] A mobile device can have any number of variations. For example, a payment application can include a payment authorization module configured to generate request data and receive response data. In at least some embodiments, a software development kit (SDK) library of the payment application can be used to generate the payment authorization module.

[0012] As another example, the payment application can be configured to provide a user interface on a display of the mobile device. For yet another example, a communication mechanism can be configured to receive identification data that uniquely identifies a product dispenser from the product dispenser, and the request data includes the identification data.

[0013] For another example, the communication mechanism can include a wireless transceiver configured to establish a secure connection between the mobile device and the product dispenser. In at least some embodiments, the wireless transceiver can be a Bluetooth Low Energy (BLE) transceiver.

[0014] For yet another example, the mobile device can further include a second communication mechanism configured to establish a wireless connection between the mobile device and a network cloud server.

[0015] For another example, the response data can include a security key, and the processor can be configured to use the security key in secure communication between the mobile device and the product dispenser. In at least some embodiments, the processor can be configured to use the security key to decrypt encrypted data received from the product dispenser via the secure connection (e.g., status data indicating at least one of the current state of the product dispenser and the amount of product that has been dispensed via the product dispenser), and / or the processor can be configured to use the security key to encrypt payment data that indicates the total amount of payment for a product that can be dispensed from the product dispenser, and the processor can be configured to transmit the encrypted payment data to the product dispenser.

[0016] For another example, the mobile device can include a device integrated into a motor vehicle. For yet another example, the mobile device can include one of a phone, a tablet computer, a laptop computer, and a smartwatch.

[0017] For yet another example, the processor can be configured to process payments in association with a customer loyalty program not associated with a merchant providing the product dispenser. For another example, the processor can be configured to process payments in association with a customer loyalty program associated with a merchant providing the product dispenser.

[0018] For yet another example, the product can be fuel, and the product dispenser can be a fuel dispenser. For yet another example, the product can be one of the consumables, including one of drinking liquid, electricity, air, lottery, and food.

[0019] In another aspect, a method of using a product dispenser is provided. In one embodiment, the method includes receiving, at the product dispenser via a wireless communication link, a request from a mobile device to establish a secure connection between the product dispenser and the mobile device, and, after receiving the request to establish the secure connection, receiving, via the wireless communication link, a security key from the mobile device for secure communication between the product dispenser and the mobile device. The method further includes establishing a secure connection between the product dispenser and the mobile device. The secure connection allows communication between the product dispenser and the mobile device using the security key. The method further includes, in response to receiving an authorized payment amount for a product from the mobile device, causing the product to be dispensed from the product dispenser. The authorized payment amount is encrypted using the security key.

[0020] The method may have any number of variations. For example, the method may include transmitting, to the mobile device, identification data that uniquely identifies the product dispenser before receiving the security key from the mobile device and in response to receiving the request to establish the secure connection. For another example, the security key may be received by the product dispenser regardless of whether the product dispenser has established a connection with a network cloud server. For yet another example, the method may include transmitting, via the established secure connection, status data indicating the current status of the product dispenser from the product dispenser to the mobile device. In at least some embodiments, the wireless communication link may include a BLE transceiver. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The present disclosure will be more fully understood from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0022] Figure 1 is a schematic diagram of one embodiment of a system including a product dispenser and a mobile device;

[0023] Figure 2 is a schematic diagram of one embodiment of a fuel dispenser;

[0024] Figure 3 is a flowchart of one embodiment of a method of operating a mobile device;

[0025] Figure 4 is a flowchart of one embodiment of a method of operating a product dispenser;

[0026] Figure 5A is a first part of a schematic flowchart of one embodiment of a mobile device payment transaction with a product dispenser;

[0027] Figure 5B is Figure 5A a second part of the schematic flowchart of;

[0028] Figure 6 is a flowchart showing an embodiment of a method of operating a product dispenser when a secure connection between the product dispenser and a mobile device has been prematurely interrupted; and

[0029] Figure 7 is a schematic diagram of an embodiment of a portion of a fuel dispenser. DETAILED DESCRIPTION

[0030] Certain exemplary embodiments will now be described to provide an overall understanding of the structures, functions, manufacturing, and use principles of the devices and methods disclosed herein. One or more examples of these embodiments are shown in the drawings. Those skilled in the art will understand that the devices and methods specifically described and shown in the drawings are non-limiting exemplary embodiments, and the scope of the present invention is defined only by the claims. Features shown or described in connection with one exemplary embodiment can be combined with the features of other embodiments. Such modifications and variations are intended to be included within the scope of the present invention.

[0031] Furthermore, in the present disclosure, components with the same name in the embodiments generally have similar features, and thus, within a particular embodiment, it is not necessary to describe in complete detail each feature of each component with the same name. Additionally, to the extent that linear or circular dimensions are used in the description of the disclosed systems, devices, and methods, such dimensions are not intended to limit the types of shapes that can be used in conjunction with such systems, devices, and methods. Those skilled in the art will recognize that for any geometry, the equivalents of such linear and circular dimensions can be readily determined.

[0032] Various exemplary methods and devices for electronic communication of a product dispenser are provided. Generally, a product dispenser can be configured to communicate with a mobile device when the mobile device is near the product dispenser. The mobile device can have a communication mechanism, such as a wireless transceiver, which is configured to detect the product dispenser near the mobile device. The mobile device can have a payment application that allows the use of the mobile device to pay for products that can be dispensed from the product dispenser. The payment application can be in electrical communication with a mobile payment provider that processes payments made via the mobile device. The mobile device can be configured to communicate with a network cloud server electrically to access a cloud authorization service. In particular, the mobile device can access the network cloud server via a wireless connection to request authorization of the payment application of the mobile device, which is performed regardless of whether the product dispenser has established a connection with the network cloud server. Once a response to the request is received at the mobile device, the payment application can be configured to communicate with the product dispenser regarding the dispensing of products by the dispenser and regarding the payment for products via the mobile device. Thus, payments for products that can be dispensed from the product dispenser can be processed even if the product dispenser has not established a connection with the network cloud server.

[0033] A payment application of a mobile device may be associated with or may include a payment authorization module configured to generate a request to authenticate the mobile application at a network cloud server and receive a response from the network cloud server. The payment authorization module may be generated at the mobile device using a software development kit (SDK) library.

[0034] A product dispenser may be configured to receive, via a wireless communication link, a request to establish a secure connection between the product dispenser and the mobile device. The product dispenser may be configured to transmit, in response to receiving the request to establish a secure connection, identification data that uniquely identifies the product dispenser to the mobile device. The mobile device may then use the identification data to obtain authorization for a payment application of the mobile device such that once authorized, the payment application permits the product dispenser to dispense a product and receive user instructions related to payment for the product. The product dispenser may be a fuel dispenser configured to dispense fuel. In addition to or instead of being capable of dispensing fuel, the product dispenser may be configured to dispense consumables including at least one of drinking liquid, electricity, air, lottery tickets, and food.

[0035] Figure 1 An embodiment of a system 100 is shown that includes a product dispenser 102 and a mobile device 104 configured to communicate electrically with a network cloud server 106 and with a mobile payment provider 108. The mobile device 104, which may be a telephone, tablet computer, laptop computer, smartwatch, a device integrated into a motor vehicle, or other type of mobile device, is configured to communicate with the product dispenser 102 via a communication mechanism 110. In this embodiment, the communication mechanism 110 includes a wireless transceiver, such as a low energy (BLE) transceiver. The communication mechanism 110 is configured to establish a secure connection 112 via a wireless connection between the mobile device 104 and the product dispenser 102. The product dispenser 102 in turn includes a wireless communication link 114, which in the illustrated embodiment is a BLE module. The communication link 114 includes suitable circuitry, interfaces, and code configured to transmit and / or receive radio signals via an interface such as a BLE air interface and convert the signals into corresponding signals that may be suitable for further processing in a processor of the product dispenser 102. The secure connection 112 between the product dispenser 102 and the mobile device 104 may thus be a connection such as a BLE connection, such that the communication mechanism 110 of the mobile device 104 detects the product dispenser 102 when the product dispenser 102 is in the vicinity of the mobile device 104. In Figure 1 which only by way of example the BLE connection is shown as being able to establish any private wireless network connection.

[0036] As Figure 1As shown, although the mobile device 104 may include other components, the mobile device 104 also includes a mobile payment application 116, a processor 120, and a display 121. The processor 120 can be any suitable processor configured to execute the mobile payment application 116, and the display 121 is any suitable type of display (e.g., a touchscreen display) configured to present a user interface provided by the payment application 116. The mobile payment application 116 includes a payment authorization module 118 (also referred to herein as the "mobile payment authorization SDK") generated using a software development kit (SDK) library of the payment application 116. The payment application 116 can be a payment application installed on the computing hardware of the mobile device 104 and configured to be executed by the processor 120 of the mobile device 104. The payment authorization module 118 enables the payment application 116 to be authorized by the network cloud server 106 via a wireless connection 122, regardless of whether the product dispenser 102 is connected to the network cloud server 106. As Figure 1 shown, the mobile device 104 can have a second communication mechanism 111 configured to establish a wireless connection 122 between the mobile device 104 and the network cloud server 106.

[0037] In Figure 1 an embodiment, although the network cloud server 106 may include other components, the network cloud server 106 includes a mobile application authorization infrastructure 124 and a loyalty program gateway 125. In the illustrated embodiment, as discussed in more detail below, the payment authorization module 118 of the mobile device 104 transmits a request to the network cloud server 106 to authorize the payment application 116 and once the mobile application authorization infrastructure 124 of the network cloud server 106 authorizes the payment application 116, the mobile application authorization infrastructure 124 transmits a security key 126 to the mobile payment authorization module 118. The payment authorization module 118 then provides the security key 126 to the product dispenser 102 via a secure connection 112 between the mobile device 104 and the product dispenser 102. The security key 126 is used in secure communication between the mobile device 104 and the product dispenser 102 via the connection 112, as discussed in more detail below.

[0038] As Figure 1As shown, product dispenser 102 includes a secure dispenser computer 130 and a product controller 132 coupled to the secure dispenser computer 130. The secure dispenser computer 130 can be a microcomputer. Regardless of its specific configuration, the secure dispenser computer 130 is configured to instruct the product controller 132 to dispense a product when the payment application 116 of the mobile device 104 is authorized to perform a payment for the product. The dispenser computer 130 has a communication module 134, which includes a mobile payment module 136 configured to communicate with the payment authorization module 118 of the mobile device 104 via a Bluetooth connection or a private wireless network established between the payment authorization modules 118 of the mobile payment application 116. In at least some embodiments, the product controller 132 includes iGEM computer electronics that include a remotely programmable operating system with two-channel serial communication that can support Dart, IFSF, and the current loop protocol. As in the illustrated embodiment, the product dispenser 102 can be a fuel dispenser, the product can include fuel, and the product controller 132 can be a fuel controller configured to control the amount of fuel dispensed from the fuel dispenser.

[0039] The mobile payment module 136, configured to communicate with the payment authorization module 118 of the mobile device 104, allows the product dispenser 102 to act as an independent dispenser for mobile payment transactions that communicates with the mobile device 104 to receive verification (or rejection) of the customer's mobile payment information. As described above, conventional mobile payment methods rely on on-site dispenser controllers and / or product dispenser authorization by a network cloud infrastructure such as the network cloud server 106, which requires one or both of the product dispenser and the on-site controller to communicate with the network cloud. However, the connectivity between the dispenser and the cloud creates an intermediary point that can potentially be accessed fraudulently. In contrast, Figure 1 the system 100 and other systems disclosed herein provide a secure way to dock the mobile device 104 directly with the product dispenser 102 via the mobile payment application 116, thus allowing different types of payments to be processed. Also, merchants providing the product dispenser 102 for use in the system 100 can use an infrastructure with fewer components and thus have lower installation and maintenance costs.

[0040] As described above, the product dispenser 102 can dispense a product, where payment therefor is processed via the mobile device 104, regardless of whether the product dispenser 102 has established a connection with the network cloud server 106. In at least some embodiments, it is not necessary for the product dispenser 102 to have Internet connectivity to conduct a product dispensing transaction. Thus, the described technology allows for providing a stand-alone environment for product dispensing (e.g., fuel dispensing), in which the product dispenser 102 is autonomous and is made to operate entirely via the mobile device 104 that communicates with the product dispenser 102 via the connection 112. However, in some embodiments, the product dispenser 102 can be configured to communicate with the network cloud server 106 and / or one or more other network cloud servers for other purposes. In these embodiments, at least one processor of the product dispenser 102 is configured to execute cloud service software for communicating with the network cloud server 106 and / or the other network cloud server(s). For example, the product dispenser 102 can include a computing system, such as a Raspberry Pi, an Arduino Uno, or a CHIP computer, that includes a processor and a memory storing cloud service software executable by the processor. In some embodiments, the product dispenser 102 can have a connection established with the network cloud server 106 and / or the other network cloud server(s), and although authorization of the mobile application 116 occurs independently of that connection, the product dispenser 102 can receive various information (e.g., media data, etc.) from the network cloud server 106 and / or the other network cloud server(s), and / or the product dispenser 102 can communicate with the other network cloud server(s) and / or the network cloud server 106 for other reasons (e.g., receiving an upgrade, providing metrics and analytics information to the cloud, etc.).

[0041] The mobile payment application 116 can be configured to communicate electrically with the dispenser computer 130 to authorize the dispenser 102 to dispense a product based on an authorized mobile transaction. In this way, the mobile payment application 116 can accept types of payment that may not be accepted by conventional systems that rely on a connection between the product dispenser 102 and the network cloud server 106. Thus, the mobile payment application 116 can allow a merchant with the product dispenser 102 to accept any suitable type of payment, such as a credit card, a debit card, a fleet fuel card, etc. In particular, an SDK library is used to configure the payment authorization module 118 such that the mobile application 116 accepts any type of payment, and the merchant can establish a relationship with a corresponding mobile payment provider, the corresponding mobile payment provider being, for example, Figure 1 the mobile payment provider 108 shown. Thus, a merchant with the dispenser can be enabled to receive one or more suitable types of payment from the mobile payment provider 108.

[0042] A merchant providing the product dispenser 102 is allowed to use any desired customer loyalty program. The merchant typically uses one loyalty program associated therewith, which may be integrated with a point-of-sale (POS) system. The embodiments described herein allow the merchant to use multiple customer loyalty programs, including customer loyalty programs not associated with the merchant and customer loyalty programs associated with the merchant. Thus, the payment application 116 of the mobile device 104 can process payments for products dispensable from the product dispenser 102 in association with any of one or more customer loyalty programs that would otherwise not be available to the merchant. In this way, the mobile device 104 can be used to pay for fuel and other products using various payment methods, which can be used in association with any suitable services that the merchant is enabled to provide.

[0043] A payment transaction can be performed via the mobile device 104 such that direct user interaction with the product dispenser 102 is not required. Thus, there is no need to accept physical payments at the product dispenser 102. Once the mobile device 104 detects the product dispenser 102 in the vicinity of the mobile device 104, the mobile device 104 can begin communicating with the product dispenser 102. For example, when the user has approached the product dispenser 102 and the communication mechanism of the mobile device 104 (e.g., Figure 1 the communication mechanism module 110 in ) detects the product dispenser 102, a BLE or other short-range communication connection 112 is initiated between the user's mobile device 104 and the product dispenser 102. Once the connection 112 is established, the mobile device 104 and the product dispenser 102 communicate to dispense the product from the product dispenser 102 and to process the payment for the product.

[0044] As described above, in at least some embodiments, the mobile device 104 can include a device integrated into a motor vehicle. For example, the dashboard or other parts of the vehicle can have a display configured to present a user interface provided by a mobile application. In this way, a user of the vehicle can perform a payment transaction without having to leave the vehicle.

[0045] The product dispenser 102 may not have the components required to accept physical payments at the product dispenser 102. Thus, a lower-cost dispenser can be utilized, and the entire payment transaction can be performed via the mobile device 104.

[0046] As will be understood by those skilled in the art, Figure 1 the components shown in can have many variations and they can include Figure 1Other components not shown. For example, in an implementation where the product dispenser has a display, the product dispenser 102 can include a media module configured to access, for example, media services from a network cloud that permit visual and / or auditory media to be provided by the product dispenser. The product dispenser 102 can also have other modules, such as a fuel management module, a monitoring and analytics module, and any other modules. Non-limiting examples of modules that can be included in the product dispenser are described in U.S. Patent Application No. 15 / 182,201, filed on June 16, 2016, and titled "Methods And Devices For Fuel Dispenser Electronic Communication", the entire content of which is incorporated herein by reference.

[0047] such as Figure 1 A product dispenser, such as the fuel dispenser 102, can have various configurations, and as described above, in some implementations, the product dispenser includes a fuel dispenser configured to dispense fuel and interact with a mobile device regarding payment for the fuel. Figure 2 An embodiment of a fuel dispenser 202 is shown, which includes an electronics compartment 204, a pump compartment 206, a nozzle 208, and an antenna 210. The electronics compartment 204 has therein electronics for facilitating payment for fuel and for facilitating the dispensing of fuel. The electronics include a controller 212, a communication link 213 configured to provide wired and / or wireless communication (e.g., with a network cloud), a communication module 214 (e.g., Figure 1 the wireless communication link 114 in Figure 1 ) configured to communicate electrically with a mobile device (e.g.,

[0048] The pump compartment 206 includes a pump 222 configured to pump fuel from a fuel tank or other reservoir and includes a fuel meter 224 configured to monitor fuel flow. As will be understood by those skilled in the art, the pump compartment 206 may include other elements that facilitate fuel dispensing, such as valves, vapor recovery systems, and the like. The pump compartment 206 is isolated from the electronics compartment 204 within the fuel dispenser 202 to promote safety, security, and / or maintenance, as will be understood by those skilled in the art. Accordingly, fuel is not permitted to flow from the pump compartment 206 to the electronics compartment 204 and instead flows from the pump compartment 206 to the nozzle 208 for dispensing. The nozzle 208 includes one or more nozzles, each configured to dispense fuel from the fuel dispenser as pumped therefrom by the pump 222. The antenna 210 is configured to facilitate communication over the communication link 213.

[0049] Figure 3 An embodiment of a process 300 for operating a mobile device such as Figure 1 the mobile device 104 is shown. The process 300 may begin at any suitable time, e.g., when the mobile device detects 302 a product dispenser in the vicinity of the mobile device. For example, a user of a BLE-enabled mobile device may approach a product dispenser, e.g., on foot, in a vehicle, etc., such that the mobile device is within the range of the BLE beacon of the product dispenser, the product dispenser being, for example, Figure 1 the product dispenser 102. The communication mechanism of the mobile device may detect a product dispenser in the vicinity of the mobile device. The process may begin when a mobile payment application on the mobile device is launched, which may occur in response to the detection of the product dispenser. Alternatively, in some cases, the mobile payment application may be initiated upon another trigger, another trigger such as user input received via the display of the mobile device or in another manner.

[0050] Regardless of how the mobile device detects 302 the product dispenser and initiates the process 300, the process 300 includes transmitting 304, e.g., via the communication mechanism, a request to establish a secure connection with the product dispenser. In response, the mobile device receives 306 identification data from the product dispenser that uniquely identifies the product dispenser. The process 300 includes transmitting 308 request data via a wireless connection to a network cloud server (e.g., Figure 1 the network cloud server 106) that requests authorization for the payment application of the mobile device. The request data includes the identification data that uniquely identifies the product dispenser. In response to the transmission of the request data, the process includes the mobile device receiving 310 response data via the wireless connection from the network cloud server that indicates that the payment application has been authorized to process payments for products that can be dispensed from the product dispenser. The response data includes a security key that the processor of the mobile device is configured to use in secure communication between the mobile device and the product dispenser.

[0051] Once the payment application is authorized, the mobile device communicates 312 with the product dispenser regarding the amount of payment and the status of dispensing a product from the product dispenser. The mobile device transmits a security key to the product dispenser, and a processor of the mobile device can use the security key to decrypt encrypted data received from the product dispenser via a secure connection. As discussed in more detail below, the encrypted data includes status data that indicates at least one of the current status of the product dispenser and the amount of product that has been dispensed via the product dispenser. The communication 312 includes, for example, receiving via a display of the mobile device or automatically the total payment amount for a product that can be dispensed from the product dispenser. The processor of the mobile device is configured to encrypt payment data indicating the total payment amount using the security key, and the encrypted payment data is transmitted to the product dispenser. When the product dispensing and payment for the product are completed, the process 300 can end, which can be done automatically or upon triggered activation.

[0052] Figure 4 An embodiment of a process 400 using a product dispenser such as Figure 1 product dispenser 102 is shown. For example, the process 400 can start when a mobile device 104 such as Figure 1 detects a product dispenser in its vicinity. The process 400 includes receiving 402 at the product dispenser via a wireless communication link a request to establish a secure connection between the product dispenser and the mobile device. In response to receiving the request to establish a secure connection, the product dispenser transmits 404 to the mobile device identification data that uniquely identifies the product dispenser. After receiving the request to establish a secure connection, the process 400 involves receiving 406 via the wireless communication link from the mobile device a security key for secure communication between the product dispenser and the mobile device. Then a secure connection 408 is established between the product dispenser and the mobile device, where the secure connection allows communication with the mobile device using the security key.

[0053] In addition, the product dispenser receives 410 from the mobile device an authorized payment amount for the product, where the authorized payment amount is encrypted using the security key. In response to receiving the authorized payment amount for the product, the process 400 further includes causing 412 the product to be dispensed from the product dispenser. The product dispenser communicates 414 with the mobile device regarding the payment amount and the status of dispensing the product from the product dispenser.

[0054] Figures 5A - 5B An embodiment of a process 500 showing the interaction between a product dispenser 502, a mobile device 504, and a network cloud server 506 is shown. The product dispenser 502, the mobile device 504, and the network cloud server 506 can be, for example, Figure 1Product dispenser 102, mobile device 104, and network cloud server 106. In this embodiment, product dispenser 502, which is a fuel dispenser configured to dispense fuel, includes wireless communication link 514, dispenser computer 530, and product controller 532. Dispenser computer 530 can be, for example Figure 1 dispenser computer 130, and has a communication module that includes a mobile payment module, such as a mobile payment module Figure 1 mobile payment authentication SDK communication module 136. The mobile payment module of dispenser computer 530 can perform Figures 5A - 5B the processes shown in. As Figures 5A - 5B shown in, mobile device 504 includes a user interface, mobile payment application 516 (e.g., Figure 1 mobile payment application 116), and payment authorization module 518 (e.g., Figure 1 payment authorization module 118), which can be generated using a software development kit (SDK) library. As described above, mobile payment application 516 can include payment authorization module 518. Network cloud server 506 includes a cloud authorization server configured to authorize mobile payment application 516 of mobile device 504.

[0055] As Figures 5A - 5B shown in, user input is received at mobile device 504 via user interface 505. The user input instructs mobile device 504 to start (or initiate) mobile payment application 516. Once mobile payment application 516 is started, payment authorization module 518 is initialized and begins searching for BLE or other connection signals that can be emitted by the product dispenser.

[0056] Dispenser computer 530 (its mobile payment module) requests information about available fuel supply points from fuel controller 532 ("request fuel supply points"), and is responded to with appropriate information about the fuel supply points ("return fuel supply points"). Information about available fuel supply points indicates to dispenser computer 530 at least one fuel dispenser or point available for dispensing fuel. Fuel dispenser 506 can contain multiple dispensers (and thus multiple pumps), and thus fuel controller 532 can control more than one fuel supply point. Additionally or alternatively, a single fuel dispenser can have multiple pumps (which are controlled separately), and each of the pumps can be referred to as a fuel supply point. Regardless of the type of one or more identified fuel supply points, dispenser computer 530 can transmit the available fuel supply points and fuel supply site IDs via wireless communication link 514 ("broadcast fuel supply points and site IDs"). This broadcast information is transmitted to payment authorization module 518 of mobile device 504 via communication link 514 of product dispenser 502 and the communication mechanism of the mobile device.

[0057] Once a BLE or other connection signal transmitted from a fuel supply point is detected by the mobile device 504, that fuel supply point (in the illustrated embodiment, the fuel dispenser 502) is added to the list of devices with which the mobile device 504 communicates. In Figures 5A - 5B only one fuel supply point (dispenser 502) is shown for purposes of illustration and discussion, but as noted above, multiple fuel supply points may communicate with the mobile device 504. The list of devices is stored in the memory of the mobile device 504. The fuel dispensers in the list may be ranked based on the strength of the communication signal between each fuel dispenser and the mobile device. In this way, the mobile device 504 may request the establishment of communication between the mobile device 504 and the fuel dispenser closest to the mobile device, and thus the signal transmitted by that dispenser and detected by the mobile device is stronger than signals detected from other dispensers.

[0058] In the illustrated embodiment, as Figures 5A - 5B shown, the mobile payment application 516 instructs the user interface 505 on the display of the mobile device 504 to display information about available fuel supply points ("List fuel supply points by signal strength") in combination with information about the signals received by the mobile device from the respective fuel supply points. Information about the fuel supply points may be displayed on the user interface 505 in association with other information that may assist a customer (e.g., the user of the mobile device 504) in making a decision about selecting a fuel dispenser. For example, information about fuel grades and numbers and / or other identification information about the fuel supply points may be displayed. Moreover, the user interface 505 may display one or more appropriate prompts requesting user input, which may be presented in any suitable format.

[0059] Further, as Figures 5A - 5BAs shown, the user interface receives an input indicating selection of a fuel dispenser from a displayed list of fuel supply points ("Select Fuel Supply Point"). Although the fuel dispenser can be selected automatically, an input can be received from the user. For example, the fuel dispenser closest to the mobile device can be selected automatically, or the fuel dispenser can be selected based on other factors (e.g., user preferences known to the mobile payment application 516). In response to this input, the mobile payment application 516 sends a request to the mobile payment authorization SDK 518 to initiate a connection with the selected fuel dispenser ("Initiate Dispenser Connection"). The mobile payment authorization SDK 518 transmits a request over the communication link 514 to the product dispenser 502 to establish a secure connection with the product dispenser 502 ("Request Connection"). For the purposes of describing this embodiment, the product dispenser 502 can be considered as the fuel supply point selected based on instructions received via the user interface 505, or can be selected in another way as described above. The mobile payment authorization SDK 518 is configured to receive, via the communication mechanism of the mobile device 504, identification data that uniquely identifies the product dispenser 502, such as a unique fuel supply point ID code.

[0060] The mobile payment authorization SDK 518 uses the processor of the mobile device 504 to transmit request data ("Authorize Application") over a wireless connection between the mobile device 504 and the network cloud server 506 to request authorization for the payment application 516 on the mobile device 504. The request data can include the identification data that uniquely identifies the product dispenser 502. In response to this request data, the processor of the mobile device 504 receives response data ("Application Authorization") from the network cloud server 506 over the wireless connection, which indicates that the payment application 516 has been authorized to process payments for products (fuel, in this embodiment) that can be dispensed from the product dispenser 502. The response data includes a security key that will be used in secure communication between the mobile device 504 and the product dispenser 506. As described above, this security key is received by the product dispenser, regardless of whether the product dispenser has established a connection with the network cloud server. If the network cloud server 506 does not authorize the application 516, the response data transmitted from the network cloud server 506 to the mobile device 504 indicates a lack of authorization. The mobile device 504 can display an indication of the failed authorization on the user interface 505, which can prompt the user to try authorizing again or select another fuel supply point to be authorized.

[0061] As Figures 5A - 5B shown, the response data ("Application Authorization") including the security key is transmitted from the network cloud server 506 to the mobile payment authorization SDK 518 of the mobile device 504. Also, although in Figures 5A - 5BNot shown in the figure, the mobile device 504 transmits a security key to the product dispenser 502, and the product dispenser 502 receives the security key. Once the product dispenser 502 receives the security key (also referred to as the "encryption key"), as Figures 5A - 5B shown, the product dispenser 502 transmits a signal ("accept connection using encryption key") to accept a connection from the mobile device 504. In this way, a secure connection is established between the product dispenser 502 and the mobile device 504. As described above, in at least some embodiments, a secure connection such as a BLE connection is established between the communication link of the product dispenser 502 (e.g., Figure 1 communication link 114) and the communication mechanism of the mobile device 504 (e.g., Figure 1 communication mechanism 110).

[0062] Once a secure connection is established between the product dispenser 502 and the mobile device 504, the mobile payment application 516 instructs the user interface 505 to display information related to the purchase of the product and the payment for the product ("display transaction details"). This information may include the type of product available for dispensing, the price, options for selecting a certain quantity of product items (or product volume), etc. Since the product is fuel in the illustrated embodiment, the information displayed on the user interface 505 includes information related to the purchase of fuel, such as the available fuel grades, available additives, the prices of various grades and additives, information about the selected fuel dispensing point, and other relevant information. The user interface 505 may also include information associated with the user of the mobile device 504, such as, for example, user preferences, the history of using this particular fuel dispensing point or this fuel station (e.g., previous purchase information), information about other products purchased at this location via the mobile payment application 516, etc. Then, the user interface 505 receives user input related to the user's selection of one or more options related to the fuel purchase transaction, such as the amount of fuel to be dispensed and / or the total amount of payment for the fuel. Thus, as shown by the example in Figures 5A - 5B , the mobile payment application 516 receives from the user interface 505 an authorized transaction value or amount ("authorized transaction volume") indicating the total amount of payment for the fuel along with other information.

[0063] The mobile payment application 516 sends (“sends transaction details”) data with transaction details of the authorized transaction volume to the mobile payment authorization SDK 518, and the mobile payment authorization SDK 518 encrypts the data (“encrypts the data”) using a security key. Then, the mobile payment authorization SDK 518 transmits (“sends encrypted authorization volume”) the encrypted data including the encrypted authorized transaction volume to the communication link 514 of the product dispenser 502 via the communication mechanism of the mobile device. The communication link 514 provides the encrypted data to the dispenser computer 530, and the dispenser computer 530 decrypts the data using the security key and then transmits a control signal (“sends fuel supply point authorization request”) to the fuel controller 532 to enable the fuel controller 532 to dispense fuel from the fuel dispenser 502 (“allows fuel supply”). In this way, the dispenser computer 530 authorizes the fuel controller 532 to use the transaction volume to dispense the quantity of the product that can be purchased.

[0064] When the fuel controller 532 starts to dispense fuel, the fuel controller 532 transmits a corresponding signal (“sends start of fuel supply”) to the dispenser computer 530. Information about the start of the fuel supply is transmitted (“sends start of fuel supply”) to the mobile payment application 516, which causes the information to be displayed (“displays fuel supply status screen”) on the user interface 505 of the mobile device 504.

[0065] As the fuel dispensing starts and proceeds, the dispenser computer 530 monitors the status of the fuel supply (“waits for status update”), and the status of the fuel supply indicates the current status of the product dispenser 502. The fuel controller 532 updates (“updates fuel supply status”) the fuel supply status and provides (“sends status update”) a corresponding update to the dispenser computer 530. When it receives one or more fuel supply status updates, the dispenser computer 530 encrypts (“encrypts data”) the status update information and transmits the encrypted status update data (“sends encrypted status update”) to the mobile payment authorization SDK 518 of the mobile device 504. The mobile payment authorization SDK 518 decrypts the encrypted status update data using the security key and provides (“sends status update”) the decrypted status update data to the mobile payment application 516, which causes the information about the fuel supply status to be displayed (“displays status update”) on the user interface 505.

[0066] As the fuel dispensing further proceeds, and as the dispenser computer 530 continues to monitor the status of the fuel supply, the fuel controller 532 sends a signal (“sends fuel supply completion message”) to the dispenser computer 530 indicating that the fuel dispensing is completed. As Figures 5A - 5BAs shown, when the fuel dispensing is complete, the dispenser computer 530 requests ("requests final transaction details") information about the transaction from the fuel controller 532, and in response to the request, the fuel controller 532 provides ("sends final transaction details") such information to the dispenser computer 530. The dispenser computer 530 encrypts ("encrypts data") the received final fuel supply transaction information and transmits ("sends encrypted final transaction details") it to the mobile payment authorization SDK 518 of the mobile device 504. If the amount of fuel dispensed does not correspond to the authorized transaction volume (e.g., given the authorized amount, more or less fuel has been dispensed than should have been), the fuel supply transaction information indicates the difference to the mobile payment application 516, and the mobile payment application 516 is used to resolve the difference. The mobile payment authorization SDK 518 decrypts the encrypted fuel supply transaction information using a security key and provides ("sends final transaction data") the corresponding decrypted information to the mobile payment application 516, which in turn causes the fuel supply transaction information to be displayed ("displays final transaction details") on the user interface 505.

[0067] The user interface 505 displays the fuel supply transaction information in a manner that allows user input to be received regarding the displayed information. For example, user input can be received via the user interface 505 that indicates the user's approval ("accepts final transaction") of the fuel dispensing transaction (e.g., the amount of fuel dispensed and the payment amount for the dispensed fuel). In the illustrated embodiment, when the mobile payment application 516 receives such information, the mobile payment application 516 transmits receipt information to the mobile payment authorization SDK 518, as Figures 5A - 5B shown. The mobile payment authorization SDK 518 communicates with the mobile payment provider (e.g., Figure 1 mobile payment provider 108) regarding the payment for the fuel. As a result, the mobile payment authorization SDK 518 returns ("returns receipt") the receipt information to the mobile payment application 516, and the mobile payment application 516 causes the receipt information to be displayed ("displays receipt") on the user interface 505.

[0068] When fuel dispensing and payment for the fuel are completed, the secure connection between the mobile device 504 and the product dispenser 502 can be terminated. This can occur automatically when fuel dispensing and payment for the fuel are completed. Additionally, if the product dispenser 502 is no longer within the range of the communication mechanism of the mobile device 504, the connection can be stopped. As another example, the user interface 505 of the mobile device 504 can receive an instruction that directs the mobile payment application 516 to disconnect from the product dispenser 502. Regardless of how the termination of the connection between the mobile device 504 and the product dispenser 502 is triggered, the mobile payment authorization SDK 518 transmits a signal ("disconnect") to the communication link 514 of the product dispenser 502, which indicates that the connection between the mobile device 504 and the product dispenser 502 has been terminated. Then, the communication link 514 notifies ("update connection status") the dispenser computer 530 that the secure connection between the product dispenser 502 and the mobile device 504 has been disconnected.

[0069] In some cases, after product dispensing has begun, the secure connection between the product dispenser and the mobile application executing on the mobile device 504 can be interrupted. If the interrupted connection has not been re-established by the time product dispensing is completed, the product dispenser can complete a payment transaction to complete payment for the dispensed product in an alternative manner. For example, the product dispenser can communicate electrically with a network cloud server (e.g., the network cloud server with which the mobile device communicates or another network cloud server), which can be accomplished by establishing a direct connection between the product dispenser and the network cloud server or via the mobile payment use (payment authorization module, such as Figure 1 the mobile payment authorization SDK 118) of the next customer of the mobile device that establishes a subsequent secure connection with the product dispenser. Thus, the product dispenser can be configured to establish an alternative connection to complete the dispensing of the product in response to detecting that the secure connection between the product dispenser and the mobile device has been interrupted and has not been re-established by the time product dispensing is completed.

[0070] Figure 6 illustrates operating a product dispenser (e.g., Figure 1 the product dispenser 102 of Figures 5A - 5BAn embodiment of a process 600 for establishing an alternative connection (e.g., with product dispenser 502 or any other product dispenser described herein) when a secure connection between the product dispenser and the mobile device does not exist upon completion of product dispensing. In process 600, a secure connection is established 602 between the product dispenser and the mobile device, and then the product is dispensed 604, as described above. If it is determined 606 that the secure connection between the product dispenser and the mobile device has been interrupted and not re-established yet when the product has been dispensed, payment for the dispensed product is completed 608 using an alternative connection. The alternative connection can be established in various ways. For example, as described above, in some embodiments, the product dispenser can communicate with a network cloud server with which the mobile device communicates to complete a payment transaction. In some embodiments, a direct connection can be established between the product dispenser and the network cloud server and this direct connection is used to complete the payment transaction. Alternatively, in other embodiments, the product dispenser can communicate indirectly with the network cloud server via the payment authorization module of another mobile device (e.g., Figure 1 the mobile payment authorization SDK 118 or Figures 5A - 5B the mobile payment authorization SDK 518), and another mobile device establishes a secure connection with the product dispenser. In this way, the payment transaction can be completed without user intervention.

[0071] Accordingly, the methods and devices described herein can provide authorization for a product dispenser via a mobile payment application of a mobile device that has established a secure connection with the product dispenser. Since the mobile application is authorized by the network cloud server regardless of whether a connection is established between the product dispenser and the network cloud server, the product dispenser can operate as a stand-alone system that only requires a connection between the product dispenser and the mobile device. Thus, the mobile payment application interacts directly with the product dispenser, which allows additional payment methods to become available to the customer. Moreover, it enables the merchant providing the product dispenser to offer additional services to the customer. For example, while a customer loyalty program associated with the merchant can be provided, additionally, the mobile payment application can process payments in association with one or more customer loyalty programs not associated with the merchant. Accordingly, multiple loyalty programs that are not conventionally available can be offered to the customer.

[0072] Product dispensers, such as fuel dispensers, described herein can be manufactured at a lower cost. In particular, since the entire process of making payment for the product available for dispensing can be performed via a mobile device, the product dispenser may not include components required to accept physical payments at the product dispenser. Thus, the product dispenser may not have a keypad, components (e.g., (one or more) card readers) for receiving credit cards, smart cards, mobile wallets (e.g., on a mobile device) that communicate with the product dispenser via NFC (Near Field Communication) or RFID (Radio Frequency Identification) communication, etc. Nor will other related components, such as a printer for printing paper receipts, be required. Additionally, the product dispenser may not include fuel grade selection buttons, and other components required to manually enter instructions into the product dispenser.

[0073] Figure 7 An embodiment of a product dispenser 700 is shown, which in the shown embodiment is a fuel dispenser and does not have components for accepting payments via physical components of the product dispenser. As shown, the front panel 702 of the product dispenser 700 includes a display 704, which can display various information related to product dispensing or other information, such as, for example, media information. The product dispenser 700 can have a second display 706, which is configured to display information about the progress of product dispensing (e.g., fuel dispensing) or other information. In some embodiments, the product dispenser can include only one of the displays 704, 706, or the product dispenser can not have any displays. This allows for the manufacture of less expensive product dispensers that do not need to be connected to a network cloud server, which is particularly advantageous in remote locations and locations with inclement weather.

[0074] One or more aspects or features of the subject matter described herein can be implemented in digital electronic circuitry, integrated circuitry, specially designed application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), computer hardware, firmware, software, and / or combinations thereof. These various aspects or features can include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor, which can be special purpose or general purpose, coupled to receive data and instructions from, and to transmit data and instructions to, a storage system, at least one input device, and at least one output device. The programmable system or computing system can include clients and servers. The clients and servers are typically remote from each other and typically interact via a communication network. The relationship of client and server is generated by computer programs running on the respective computers and having a client - server relationship to each other.

[0075] These computer programs, which may also be referred to as programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor and can be implemented in a high-level procedural language, an object-oriented programming language, a functional programming language, a logical programming language, and / or in assembly / machine language. As used herein, the term "machine-readable medium" refers to any computer program product, apparatus, and / or device that provides machine instructions and / or data to a programmable processor, such as, for example, magnetic disks, optical disks, memory, and programmable logic devices (PLDs), including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal that provides machine instructions and / or data to a programmable processor. A machine-readable medium may non-transitorily store such machine instructions, such as, for example, would be a non-transitory solid-state memory or a magnetic hard disk drive or any equivalent storage medium. A machine-readable medium may alternatively or additionally store such machine instructions in an instantaneous manner, such as, for example, would be a processor cache or other random access memory associated with one or more physical processor cores.

[0076] To provide for interaction with a user, one or more aspects or features of the subject matter described herein may be implemented on a computer having a display device, such as, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), or a light emitting diode (LED) monitor for displaying information to the user, and a keyboard and a pointing device, such as, for example, a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with the user. For example, feedback provided to the user may be any form of sensory feedback, such as, for example, visual feedback, auditory feedback, or tactile feedback; and input received from the user may be in any form, including but not limited to audible, speech, or tactile input. Other possible input devices include, but are not limited to, a touch screen or other touch-sensitive device, such as a single-point or multi-point resistive or capacitive touchpad, speech recognition hardware and software, an optical scanner, an optical indicator, a digital image capture device and associated interpretation software, and the like.

[0077] Based on the above embodiments, those skilled in the art will understand additional features and advantages of the present invention. Thus, the present invention is not limited to what has been particularly shown and described except as indicated by the appended claims. All publications and references cited herein are hereby expressly incorporated by reference in their entirety.

Claims

1. A dispensing system, comprising: A product dispenser configured to dispense a product including at least one of the following: Fuel, which can be dispensed to a vehicle through a nozzle, Drinking liquid, Electricity, Air, Lottery tickets, and Food; Wherein the product dispenser includes: A wireless transceiver, A processor, and A memory storing instructions that, when executed by the processor, cause the processor to perform operations including: Causing first data to be wirelessly transmitted to a mobile device, where the first data includes data uniquely identifying the product dispenser, After causing the first data to be wirelessly transmitted to the mobile device, wirelessly receiving a security key from the mobile device, After wirelessly receiving the security key, establishing a secure connection with the mobile device that allows the product dispenser to communicate securely with the mobile device, and After receiving second data indicating an authorized customer payment for the product from the mobile device, allowing the product to be dispensed from the product dispenser, where the second data is wirelessly received through the secure connection and encrypted using the security key.

2. The dispensing system according to claim 1, wherein, The operations further include causing third data to be wirelessly transmitted to the mobile device during the dispensing of the product from the product dispenser; and The third data indicates the status of the dispensing of the product from the product dispenser.

3. A dispensing method, comprising: Causing first data to be wirelessly transmitted from the product dispenser to the mobile device; After causing the first data to be wirelessly transmitted to the mobile device, wirelessly receiving a security key from the mobile device at the product dispenser; After wirelessly receiving the security key, establishing a secure connection between the product dispenser and the mobile device that allows the product dispenser to communicate securely with the mobile device; And After receiving second data indicating an authorized customer payment for the product from the mobile device at the product dispenser, allowing the product to be dispensed from the product dispenser; Wherein the first data includes data uniquely identifying the product dispenser; Wherein the second data is wirelessly received through the secure connection and encrypted using the security key; and Wherein the product dispenser is configured to dispense a product including at least one of the following: Fuel, which can be dispensed to a vehicle through a nozzle, Drinking liquid, Electricity, Air, Lottery tickets, and Food.

4. The dispensing method according to claim 3, further comprising causing third data to be wirelessly transmitted from the product dispenser to the mobile device during the dispensing of the product from the product dispenser; Among them, The third data indicates the status of the dispensing of the product from the product dispenser.

5. The dispensing system according to claim 1 or the dispensing method according to claim 3, wherein, The product dispenser includes a fuel dispenser and the product includes at least fuel.

6. The dispensing system according to claim 1 or the dispensing method according to claim 3, wherein, The product includes at least electricity.

7. The dispensing system according to claim 1 or the dispensing method according to claim 3, wherein, The product includes at least one of air, lottery tickets, and food.

8. The dispensing system according to claim 1 or the dispensing method according to claim 3, wherein, In response to the product dispenser receiving an insecure request from the mobile device, causing the first data to be wirelessly transmitted to the mobile device to establish a secure connection.

9. The dispensing system according to claim 1 or the dispensing method according to claim 3, wherein, The mobile device includes one of a phone, a tablet computer, a laptop computer, and a smartwatch.

10. The dispensing system according to claim 1 or the dispensing method according to claim 3, wherein, The mobile device includes a device integrated into a vehicle.

Images