Method and apparatus for mobile payment transactions utilizing a product dispenser

Abstract

Various exemplary methods and devices for electronically communicating with a product dispenser of a mobile device are provided. In general, a mobile device can request a secure connection with a product dispenser detected near the mobile device. The mobile device can transmit request data to a network cloud server to authorize a mobile payment application executed on the mobile device, and can receive response data from the network cloud server indicating that the payment application has been authorized to process payment for a product that can be dispensed from the product dispenser. Regardless of whether the product dispenser has already established a connection with the network cloud server, the mobile device and the product dispenser use a security key included in the response data to establish a secure connection.

Description

[0001] Related Applications

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

[0003] The present disclosure relates generally to methods and apparatus for product dispenser electronic communications, and more particularly to payment transactions performed via a mobile device for payment for a product dispenseable from a product dispenser. 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 is traditionally used to control the actual dispensing of fuel by the fuel dispenser. The dispenser controller is usually in the same place as the fuel dispenser and is coupled to a store interface unit so that a site attendant can monitor and control a specific fuel supply (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 traditionally includes 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 a pump number, pump status, dispensed fuel volume, and sales price.

[0005] Point of sale (POS) systems, such as in-store POS terminals or payment modules embedded in fuel dispensers, are traditionally used to control the payment functionality of fuel dispensers. The POS system is often at the same site as the fuel dispenser and sends data signals to the fuel dispenser, providing it with various information and commands. The information traditionally includes user prompting controls, graphics, and media for display on the 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 sales price.

[0006] As mobile payments become more and more common, POS systems can accept mobile payments for fuel and other goods / services. Conventionally, in order to authorize mobile payment transactions, fuel dispensers communicate with POS systems to complete fuel purchase transactions. POS systems can operate as intermediaries between fuel dispensers and remote sources such as network clouds, hosting network cloud fuel management services. However, the existing infrastructure for mobile payments utilizing POS systems (e.g., at fuel supply service stations) is cumbersome, making it inconvenient for customers to perform payments for fuel and other goods / services at POS systems. In addition, although many customers prefer to stay outside during fuel supply to be able to use their mobile devices to pay for transactions, customers are required to enter stores (e.g., fuel supply service stations) to complete fuel purchase transactions.

[0007] Alternatively, the fuel dispenser can be enabled to communicate directly with the network cloud to authorize mobile payments. Regardless of whether the fuel dispenser communicates directly with the network cloud or communicates with the network cloud via a field dispenser controller (e.g., a POS system) that is communicatively coupled to the dispenser, the network cloud is required to transmit the mobile payment authorization information to the fuel distribution site, such as directly to the dispenser or to the dispenser controller. This creates a security risk because inbound traffic must be allowed to access the fuel distribution site, thereby subjecting secure data (e.g., payment details, customer personal identification numbers (PINs), etc.) to potential fraudulent access. Moreover, continuous connectivity between the network cloud and the fuel dispenser and / or POS system is required for conducting fuel purchase transactions. In addition, only certain types of payments are typically accepted via the POS system, which limits the payment options available to customers.

[0008] Therefore, there remains a need for improved methods and apparatus for fuel dispenser electronic communications to perform payment transactions. Summary of the invention

[0009] Generally, methods and apparatus for electronic communication of a product dispenser are provided. In particular, methods and apparatus for performing a payment transaction for a product dispensable 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 to a network cloud server via a wireless connection, the request data requesting authorization of a payment application of the mobile device, and the processor is further configured to receive response data from the network cloud server via the wireless connection, the response data indicating that the payment application has been authorized to process payment for a product that can be dispensed from the product dispenser.

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

[0012] As another example, the payment application may be configured to provide a user interface on a display of the mobile device.For yet another example, the communication mechanism may be configured to receive identification data from the product dispenser that uniquely identifies 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 may further include a second communication mechanism configured to establish a wireless connection between the mobile device and the network cloud server.

[0015] For another example, the response data may include a security key, and the processor may be configured to use the security key in secure communications between the mobile device and the product dispenser. In at least some embodiments, the processor may 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 a current state of the product dispenser and an amount of product that has been dispensed via the product dispenser), and / or the processor may be configured to use the security key to encrypt payment data indicating a total amount of payment for a product that can be dispensed from the product dispenser, and the processor may be configured to transmit the encrypted payment data to the product dispenser.

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

[0017] For yet another example, the processor may 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 may 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 may be fuel, and the product dispenser may be a fuel dispenser.For yet another example, the product may be one of consumables, including one of drinking liquid, electricity, air, lottery tickets, and food.

[0019] In another aspect, a method for using a product dispenser is provided, in one embodiment, the method comprising receiving a request from a mobile device to establish a secure connection between the product dispenser and the mobile device via a wireless communication link at the product dispenser, and, after receiving the request to establish the secure connection, receiving a security key for secure communication between the product dispenser and the mobile device from the mobile device via the wireless communication link. The method also 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 also includes, in response to receiving an authorized payment amount for the 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, prior to receiving the security key from the mobile device and in response to receiving a request to establish a secure connection, transmitting identification data that uniquely identifies the product dispenser to the mobile device. For another example, the security key may be received by the product dispenser regardless of whether the product dispenser has established a connection with the network cloud server. For yet another example, the method may include transmitting status data indicating a current status of the product dispenser from the product dispenser to the mobile device via the established secure connection. 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 distributor;

[0024] Figure 3 is a flow chart illustrating one embodiment of a method of operating a mobile device;

[0025] Figure 4 is a flow chart illustrating one embodiment of a method of operating a product dispenser;

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

[0027] Figure 5B yes Figure 5A The second part of the schematic flow chart;

[0028] Figure 6 is a flow chart illustrating one 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 one embodiment of a portion of a fuel distributor. DETAILED DESCRIPTION

[0030] Certain exemplary embodiments will now be described to provide an overall understanding of the principles of structure, function, manufacture and use of the apparatus and methods disclosed herein. One or more examples of these embodiments are shown in the accompanying drawings. It will be appreciated by those skilled in the art that the apparatus and methods specifically described herein and shown in the accompanying drawings are non-limiting exemplary embodiments, and that the scope of the present invention is limited only by the claims. The features shown or described in conjunction with an exemplary embodiment may 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] In addition, in the present disclosure, components of the same name of the embodiments generally have similar features, and therefore, within a particular embodiment, it is not necessary to fully describe in detail every feature of each component of the same name. In addition, 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 the equivalents of such linear and circular dimensions can be readily determined for any geometric shape.

[0032] Various exemplary methods and devices for electronic communication of product dispensers 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 a 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 electrically communicated with a mobile payment provider that processes payments performed via the mobile device. The mobile device can be configured to electrically communicate with a network cloud server 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 independently 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 about the distribution of the product by the distributor and about the payment of the product via the mobile device. Therefore, even if the product dispenser has not yet established a connection with the network cloud server, payment for products that can be dispensed from the product dispenser can be processed.

[0033] The payment application of the mobile device may be associated with or may include a payment authorization module configured to generate a request to authenticate the mobile application at the 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] The product dispenser may be configured to receive a request to establish a secure connection between the product dispenser and the mobile device via a wireless communication link from the mobile device. The product dispenser may be configured to transmit identification data that uniquely identifies the product dispenser to the mobile device in response to receiving the request to establish a secure connection. The mobile device may then use the identification data to obtain authorization for a payment application of the mobile device, so that once authorized, the payment application allows the product dispenser to dispense the 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 in lieu of being able to dispense fuel, the product dispenser may be configured to dispense consumables including at least one of potable liquids, electricity, air, lottery tickets, and food.

[0035] Figure 1 One embodiment of a system 100 is shown, which includes a product dispenser 102 and a mobile device 104 configured to communicate electronically with a network cloud server 106 and with a mobile payment provider 108. The mobile device 104, which may be a phone, a tablet computer, a laptop computer, a smart watch, 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 Bluetooth® Low Energy (BLE) transceiver. The communication mechanism 110 is configured to establish a secure connection 112 between the mobile device 104 and the product dispenser 102 via a wireless connection. 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 circuits, interfaces, and codes that are configured to transmit and / or receive radio signals through an interface such as a BLE air interface and convert the signals into corresponding signals, which 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. Figure 1 The BLE connection is shown by way of example only as any private wireless network connection may be established.

[0036] like Figure 1As shown in , 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 touch screen 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 a "mobile payment authorization SDK") generated using a software development kit (SDK) library for 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 the wireless connection 122, regardless of whether the product dispenser 102 is connected to the network cloud server 106. As shown in FIG. Figure 1 As shown in , the mobile device 104 may have a second communication mechanism 111 , which is configured to establish a wireless connection 122 between the mobile device 104 and the network cloud server 106 .

[0037] exist Figure 1 In the embodiment of the present invention, the network cloud server 106 includes a mobile application authorization infrastructure 124 and a loyalty program gateway 125, although the network cloud server 106 may include other components. 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 the secure connection 112 between the mobile device 104 and the product dispenser 102. The security key 126 is used in secure communications between the mobile device 104 and the product dispenser 102 via the connection 112, as discussed in more detail below.

[0038] like Figure 1As shown in , the 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 may be a microcomputer. Regardless of its specific configuration, the secure dispenser computer 130 is configured to instruct the product controller 132 to dispense the product when the payment application 116 of the mobile device 104 is authorized to execute payment for the product. The dispenser computer 130 has a communication module 134, which includes a mobile payment module 136, which is 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 module 118 of the mobile payment application 116. In at least some embodiments, the product controller 132 includes iGEM computer electronics, which includes a remotely programmable operating system with two-channel serial communication that can support Dart, IFSF, and current loop protocols. As in the illustrated embodiment, product dispenser 102 may be a fuel dispenser, the product may include fuel, and product controller 132 may be a fuel controller configured to control the amount of fuel dispensed from the fuel dispenser.

[0039] The mobile payment module 136, which is configured to communicate with the payment authorization module 118 of the mobile device 104, allows the product dispenser 102 to act as a standalone 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 product dispenser authorization by an on-site dispenser controller and / or 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. Conversely, Figure 1 The system 100 and other systems disclosed herein provide a secure way for a mobile device 104 to interface directly with a product dispenser 102 via a mobile payment application 116, thereby allowing different types of payments to be processed. Likewise, a merchant who provides a product dispenser 102 for use in the system 100 can use an infrastructure with fewer components and, therefore, fewer installation and maintenance costs.

[0040] As described above, the product dispenser 102 can be made to dispense products, wherein payment for it 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, the product dispenser 102 is not required to have Internet connectivity to conduct product dispensing transactions. Therefore, the described technology allows for providing an independent environment for product dispensing (e.g., fuel supply) in which the product dispenser 102 is autonomous and is made to operate completely through 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 communication with the network cloud server 106 and / or (one or more) other network cloud servers. For example, the product dispenser 102 may include a computing system, such as a Raspberry Pi, an Arduino Uno, or a CHIP computer, which includes a processor and a memory storing cloud service software executable by the processor. In some embodiments, product dispenser 102 may have a connection established with network cloud server 106 and / or (one or more) other network cloud servers, and although authorization of mobile application 116 occurs independently of that connection, product dispenser 102 may receive various information (e.g., media data, etc.) from network cloud server 106 and / or (one or more) other network cloud servers, and / or product dispenser 102 may communicate with (one or more) other network cloud servers and / or network cloud server 106 for other reasons (e.g., receiving upgrades, providing metrics and analytical information to the cloud, etc.).

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

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

[0043] The payment transaction can be performed via the mobile device 104 such that direct user interaction with the product dispenser 102 is not required. Thus, no physical payment needs to be accepted 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 initiate communication 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 When the communication mechanism module 110 in the embodiment 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 cause the product to be dispensed from the product dispenser 102 and to cause payment for the product to be processed.

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

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

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

[0047] Such as Figure 1 A product dispenser, such as the fuel dispenser 102 of FIG. 1 , can have a variety of 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 One 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 electronics therein for facilitating payment for fuel and for facilitating dispensing of the 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 controller 214 configured to communicate with a mobile device (e.g., Figure 1 The communication module 214 (eg, Figure 1 214), an optional display 216, a memory 218 configured to store data therein, and a processor 220. In at least some embodiments, fuel dispenser 202 may be configured for mobile payment in addition to payment through a payment terminal (not shown) at fuel dispenser 202. Processor 220 may be part of controller 212.

[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 appreciated by those skilled in the art, the pump compartment 206 may include other elements that facilitate fuel dispensing, such as valves, vapor recovery systems, etc. The pump compartment 206 is isolated from the electronic compartment 204 within the fuel dispenser 202 to facilitate safety, security and / or maintenance, as will be appreciated by those skilled in the art. Therefore, fuel is not allowed to flow from the pump compartment 206 to the electronic equipment 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 of which is configured to dispense fuel from the fuel dispenser as pumped from it by the pump 222. The antenna 210 is configured to facilitate communication via the communication link 213.

[0049] Figure 3 It shows operations such as Figure 1 104. The process 300 may begin at any suitable time, for example, when the mobile device detects 302 a product dispenser near the mobile device. For example, a user of the BLE-enabled mobile device may approach the product dispenser, such as by foot, in a vehicle, etc., so that the mobile device is within range of a BLE beacon of the product dispenser, such as a product dispenser. Figure 1 The mobile device may be configured to receive a 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 upon launching a mobile payment application on the mobile device, which may occur in response to detection of the product dispenser. Alternatively, in some cases, the mobile payment application may be initiated upon another trigger, such as user input received via a display of the mobile device or in another manner.

[0050] Regardless of the manner in which the mobile device detects 302 the product dispenser and initiates process 300, process 300 includes, for example, transmitting 304 via a 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. Process 300 includes transmitting 306 via a wireless connection to a network cloud server (e.g., Figure 1 The process includes transmitting 308 request data to the network cloud server 106 of the mobile device, the request data requesting authorization of the payment application of the mobile device. The request data includes 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 from the network cloud server via the wireless connection, the response data indicating that the payment application has been authorized to process payment for the product that can be dispensed from the product dispenser. The response data includes a security key, and the processor of the mobile device is configured to use the security key in secure communications between the mobile device and the product dispenser.

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

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

[0053] In addition, the product dispenser receives 410 an authorized payment amount for the product from the mobile device, wherein the authorized payment amount is encrypted using a security key. In response to receiving the authorized payment amount for the product, process 400 also 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] Figure 5A-5B An embodiment of a process 500 of 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 may be, for example, Figure 1The product dispenser 102, the mobile device 104 and the network cloud server 106. The product dispenser 502, which in this embodiment is a fuel dispenser configured to dispense fuel, includes a wireless communication link 514, a dispenser computer 530 and a product controller 532. The dispenser computer 530 can be, for example, Figure 1 The dispenser computer 130 has a communication module, which includes a mobile payment module, such as a Figure 1 The mobile payment authentication SDK communication module 136 of the dispenser computer 530 can execute Figure 5A-5B The processing shown in . Figure 5A-5B As shown in FIG. , the mobile device 504 includes a user interface, a mobile payment application 516 (e.g., Figure 1 ) and the payment authorization module 518 (e.g., Figure 1 The payment authorization module 118 of the mobile device 504 may be generated using a software development kit (SDK) library. As described above, the mobile payment application 516 may include a payment authorization module 518. The network cloud server 506 includes a cloud authorization server configured to authorize the mobile payment application 516 of the mobile device 504.

[0055] like Figure 5A-5B As shown in FIG. 5 , user input is received at mobile device 504 via user interface 505. The user input instructs mobile device 504 to start (or launch) mobile payment application 516. Once mobile payment application 516 is launched, payment authorization module 518 is initialized and begins searching for a BLE or other connection signal that may be transmitted by a product dispenser.

[0056] The dispenser computer 530 (and its mobile payment module) requests information about available fuel supply points from the fuel controller 532 ("Request Fuel Supply Points"), responding to it with appropriate information about the fuel supply points ("Return Fuel Supply Points"). The information about available fuel supply points indicates to the dispenser computer 530 at least one fuel dispenser or point that can be used to dispense fuel. The fuel dispenser 506 may include multiple dispensers (and therefore multiple pumps), and thus the fuel controller 532 may control more than one fuel supply point. Additionally or alternatively, a single fuel dispenser may have multiple pumps (which are controlled separately), and each of the pumps may be referred to as a fuel supply point. Regardless of the type of one or more identified fuel supply points, the dispenser computer 530 may transmit available fuel supply points and fuel supply site IDs ("Broadcast Fuel Supply Points and Site IDs") via the wireless communication link 514. The broadcast information is transmitted to the payment authorization module 518 of the mobile device 504 via the communication link 514 of the product dispenser 502 and the communication mechanism of the mobile device.

[0057] Once the BLE or other connection signal transmitted by the fuel supply point is detected by the mobile device 504, the 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. Figure 5A-5B Only one fuel supply point (dispenser 502) is shown in the figure for ease of illustration and discussion, but as described above, multiple fuel supply points can communicate with mobile device 504. A list of devices is stored in a memory of mobile device 504. The fuel dispensers in the list can be ranked based on the strength of the communication signal between each fuel dispenser and the mobile device. In this way, mobile device 504 can request to establish communication between mobile device 504 and the fuel dispenser that is closest to the mobile device, and therefore the signal transmitted by this dispenser and detected by the mobile device is stronger than the signals detected from other dispensers.

[0058] In the embodiment shown, Figure 5A-5B , mobile payment application 516 instructs user interface 505 on the display of mobile device 504 to display information about available fuel supply points ("List fuel supply points by signal strength") in conjunction with information about the signal received by the mobile device from the corresponding fuel supply points. Information about fuel supply points can be displayed on user interface 505 in association with other information that can help customers (e.g., users of mobile device 504) make decisions about selecting a fuel dispenser. For example, information about fuel grades and numbers and / or other identifying information about fuel supply points can be displayed. Moreover, user interface 505 can display (one or more) suitable prompts requesting user input, which can be presented in any suitable format.

[0059] Furthermore, if Figure 5A-5BAs shown in , the user interface receives an input indicating that a fuel dispenser is selected from the displayed list of fuel supply points ("select fuel supply point"). Although the fuel dispenser can be selected automatically, input can be received from the user. For example, the fuel dispenser closest to the mobile device can be automatically selected, or the fuel dispenser can be automatically selected based on other factors (e.g., user preferences that the mobile payment application 516 can know). In response to the 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 to the communication link 514 of the product dispenser 502 to establish a secure connection with the product dispenser 502 ("request connection"). For the purpose of describing this embodiment, the product dispenser 502 can be regarded as a fuel supply point selected based on an instruction received via the user interface 505, or can be selected in another manner as described above. Mobile payment authorization SDK 518 is configured to receive from product dispenser 502 (via the communication mechanism of mobile device 504 ) identification data that uniquely identifies product dispenser 502 , such as a unique fueling point ID code.

[0060] The mobile payment authorization SDK 518 uses the processor of the mobile device 504 to transmit request data ("Authorize Application") to the network cloud server 506 via the wireless connection between the mobile device 504 and the network cloud server 506, requesting authorization for the payment application 516 of the mobile device 504. The request data may include identification data that uniquely identifies the product dispenser 502. In response to the request data, the processor of the mobile device 504 receives response data ("Application Authorization") from the network cloud server 506 via the wireless connection, indicating 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 to be used in secure communications between the mobile device 504 and the product dispenser 506. As described above, the 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 the lack of authorization. Mobile device 504 may display an indication of the failed authorization on user interface 505, which may prompt the user to attempt authorization again or select another fueling point to be authorized.

[0061] like Figure 5A-5B As shown in , 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. Figure 5A-5B5. As not shown in FIG. 5, mobile device 504 transmits the security key to product dispenser 502, and product dispenser 502 receives the security key. Once product dispenser 502 receives the security key (also referred to as an "encryption key"), as shown in FIG. Figure 5A-5B , product dispenser 502 transmits a signal ("Connection Accepted Using Encryption Key") to accept the connection to mobile device 504. In this way, a secure connection between product dispenser 502 and mobile device 504 is established. As described above, in at least some embodiments, the communication link (e.g., Figure 1 The communication link 114) is connected to the communication mechanism of the mobile device 504 (e.g., Figure 1 A secure connection such as a BLE connection is established between the communication mechanism 110).

[0062] Once a secure connection is established between product dispenser 502 and mobile device 504, mobile payment application 516 instructs user interface 505 to display information related to the purchase of the product and payment for the product ("Display Transaction Details"). This information may include the type of product available for dispensing, the price, the option to select a certain number of product items (or product quantities), etc. Because the product is fuel in the illustrated embodiment, the information displayed on user interface 505 includes information related to purchasing fuel, such as available fuel grades, available additives, prices of various grades and additives, information about the selected fuel supply point, and other relevant information. User interface 505 may also include information associated with the user of mobile device 504, such as, for example, user preferences, history of using the particular fuel supply point or the fuel supply station (e.g., previous purchase information), information about other products purchased at the location via mobile payment application 516, etc. User interface 505 then receives user input related to the user selecting 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 Figure 5A-5B As shown in the example of , mobile payment application 516 receives from user interface 505 an authorized transaction value or amount (“authorized transaction amount”) indicating a total amount for payment of fuel along with other information.

[0063] The mobile payment application 516 sends data with transaction details including the authorized transaction amount ("Send Transaction Details") to the mobile payment authorization SDK 518, which encrypts the data using a security key ("Encrypt Data"). The mobile payment authorization SDK 518 then transmits encrypted data including the encrypted authorized transaction amount ("Send Encrypted Authorization Amount") 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, which decrypts the data using the security key and then transmits a control signal ("Send Fueling Point Authorization Request") to the fuel controller 532 to cause the fuel controller 532 to dispense fuel from the fuel dispenser 502 ("Allow Fueling"). In this way, the dispenser computer 530 authorizes the fuel controller 532 to dispense the amount of product that can be purchased using the transaction amount.

[0064] When the fuel controller 532 starts dispensing fuel, the fuel controller 532 transmits a corresponding signal ("Send Start Fueling") to the dispenser computer 530. Information about the start of fueling is transmitted ("Send Fueling Start") to the mobile payment application 516, which causes the information to be displayed ("Show Fueling Status Screen") on the user interface 505 of the mobile device 504.

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

[0066] As fuel dispensing progresses, and as dispenser computer 530 continues to monitor the status of the fuel delivery, fuel controller 532 sends ("Send Fuel Delivery Complete Message") a signal to dispenser computer 530 indicating that fuel dispensing is complete. Figure 5A-5BAs shown in , when the fuel dispense is complete, dispenser computer 530 requests (“Request Final Transaction Details”) information about the transaction from fuel controller 532, and in response to the request, fuel controller 532 provides (“Send Final Transaction Details”) such information to dispenser computer 530. Dispenser computer 530 encrypts the received final fueling transaction information (“Encrypt Data”) and transmits (“Send Encrypted Final Transaction Details”) to mobile payment authorization SDK 518 of mobile device 504. If the amount of fuel dispensed does not correspond to the authorized transaction amount (e.g., more or less fuel has been dispensed than should have been dispensed given the authorized amount), the fueling transaction information indicates the discrepancy to mobile payment application 516, and mobile payment application 516 is used to resolve the discrepancy. Mobile payment authorization SDK 518 decrypts the encrypted fueling transaction information using a security key and provides (“Send Final Transaction Data”) the corresponding decrypted information to mobile payment application 516, which in turn causes the fueling transaction information to be displayed (“Display Final Transaction Details”) on user interface 505.

[0067] The user interface 505 displays the fuel delivery transaction information in a manner that allows for receiving user input regarding the displayed information. For example, user input indicating user approval ("accepting final transaction") of the fuel dispensing transaction (e.g., the amount of fuel dispensed and the payment amount for the dispensed fuel) can be received via the user interface 505. In the illustrated embodiment, when the mobile payment application 516 receives such information, the mobile payment application 516 transmits the receipt information to the mobile payment authorization SDK 518, as shown. Figure 5A-5B The mobile payment authorization SDK 518 is shown in the figure. The mobile payment authorization SDK 518 is related to the payment for fuel with the mobile payment provider (for example, Figure 1 As a result, the mobile payment authorization SDK 518 returns (“return receipt”) receipt information to the mobile payment application 516, and the mobile payment application 516 causes the receipt information to be displayed (“display receipt”) on the user interface 505.

[0068] When the fuel dispense 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 happen automatically when the fuel dispense and payment for the fuel are completed. In addition, 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 instructs 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 ("updates the 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 may be interrupted. If the interrupted connection has not been reestablished by the time product dispensing is complete (by the time), the product dispenser may complete the payment transaction to complete payment for the dispensed product in an alternative manner. For example, the product dispenser may be in electronic communication with a network cloud server (e.g., the network cloud server with which the mobile device is communicating or another network cloud server), which may be accomplished by establishing a direct connection between the product dispenser and the network cloud server or via a mobile payment user (payment authorization module, such as a payment authorization module, such as a payment authorization module, of the next customer having a mobile device that establishes a subsequent secure connection with the product dispenser. Figure 1 Thus, the product dispenser may 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 not reestablished when the product dispensing is completed.

[0070] Figure 6 Operation of a product dispenser (e.g., Figure 1 Product dispenser 102, Figure 5A-5B502 or any other product dispenser described herein) to establish an alternative connection when a secure connection between the product dispenser and the mobile device does not exist when product dispensing is completed. 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 has not been re-established when the product has been dispensed, the alternative connection is used 608 to complete payment for the dispensed product. The alternative connection can be established in a variety of 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 the payment transaction. In some embodiments, a direct connection between the product dispenser and the network cloud server can be established and used to complete the payment transaction. Alternatively, in other embodiments, the product dispenser can communicate with the network cloud server via a payment authorization module of another mobile device (e.g., Figure 1 Mobile payment authorization SDK 118 or Figure 5A-5B The mobile payment authorization SDK 518 of the mobile device communicates indirectly with the network cloud server, 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] Therefore, the method and device described herein can provide authorization to the product dispenser via a mobile payment application of a mobile device that establishes a secure connection with the product dispenser. Because 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 an independent system that only requires a connection between the product dispenser and the mobile device. Therefore, the mobile payment application interacts directly with the product dispenser, which allows additional payment methods to become available to customers. Moreover, it enables merchants who provide product dispensers to provide additional services to customers. For example, although a customer loyalty program associated with a merchant can be provided, in addition, the mobile payment application can process payment in association with one or more customer loyalty programs that are not associated with the merchant. Therefore, multiple loyalty programs that are not conventionally available can be provided to customers.

[0072] The product dispenser such as the fuel dispenser described herein can be manufactured at a relatively low cost. In particular, because the entire process of payment for the product available for distribution can be performed via a mobile device, the product dispenser may not include the components required for accepting physical payment at the product dispenser. Therefore, the product dispenser may not have a keypad, one or more components (e.g., card reader(s)) for receiving a credit card, a smart card, a mobile wallet (e.g., on a mobile device) that communicates with the product dispenser via NFC (near field communication) or RFID (radio frequency identification) communication, etc. Other related components, such as a printer for printing paper receipts, will also not be required. In addition, the product dispenser may not include a fuel level selection button, and other components required for manually inputting instructions to the product dispenser.

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

[0074] One or more aspects or features of the subject matter described herein may be implemented in digital electronic circuits, integrated circuits, 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 may include implementations in one or more computer programs, which are executable and / or interpretable on a programmable system including at least one programmable processor, which may be dedicated or general purpose, coupled to receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, at least one input device, and at least one output device. A programmable system or computing system may include a client and a server. The client and server are typically remote from each other and typically interact through a communication network. The relationship between the client and the server is generated by means of computer programs that run on respective computers and have a client-server relationship with each other.

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

[0076] To provide 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) or a liquid crystal display (LCD) or a light emitting diode (LED) monitor, for displaying information to a user, and a keyboard and pointing device, such as, for example, a mouse or trackball, through which a user can provide input to the computer. Other types of devices may also be used to provide interaction with a user. For example, the 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 from the user may be received in any form, including, but not limited to, audible, voice, or tactile input. Other possible input devices include, but are not limited to, touch screens or other touch-sensitive devices, such as single-point or multi-point resistive or capacitive touch pads, voice recognition hardware and software, optical scanners, optical pointers, digital image capture devices and associated interpretation software, and the like.

[0077] Based on the above-described embodiments, those skilled in the art will appreciate the additional features and advantages of the present invention. Therefore, except as indicated by the appended claims, the present invention is not limited by the content specifically shown and described. All publications and references cited herein are expressly incorporated herein by reference in their entirety.

Claims

1. A mobile device, comprising: a communication mechanism configured to detect a product dispenser in proximity to the mobile device and receive identification data from the product dispenser that uniquely identifies the product dispenser; and a processor configured to transmit, via the communication mechanism, a request to establish a secure connection with the product dispenser, the processor configured to transmit, via the wireless connection, request data to a network cloud server, the request data requesting authorization of a payment application of the mobile device, and the processor 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 payment for a product dispensable from the product dispenser; Wherein the response data includes a security key, the processor is configured to use the security key in secure communications between the mobile device and the product dispenser and the request data includes identification data.

2. The mobile device according to claim 1, wherein: The payment application includes a payment authorization module configured to generate request data and receive response data.

3. The mobile device according to claim 2, wherein: Generate a payment authorization module using the payment application's software development kit (SDK) library.

4. The mobile device according to claim 1, wherein: The payment application is configured to provide a user interface on a display of the mobile device.

5. The mobile device according to claim 1, wherein: The communication mechanism includes a wireless transceiver configured to establish a secure connection between the mobile device and the product dispenser.

6. The mobile device according to claim 1 further comprises a second communication mechanism configured to establish a wireless connection between the mobile device and the network cloud server.

7. The mobile device according to claim 1, wherein: The processor is configured to use the security key to decrypt encrypted data received from the product dispenser via the secure connection.

8. The mobile device according to claim 7, wherein: The encrypted data includes status data indicating at least one of a current status of the product dispenser and an amount of product that has been dispensed via the product dispenser.

9. The mobile device according to claim 1, wherein: The processor is configured to encrypt payment data using the security key, the payment data indicating a total amount of payment for a product dispensed from the product dispenser, the processor being configured to transmit the encrypted payment data to the product dispenser.

10. The mobile device according to claim 1, wherein: Mobile devices include devices that are integrated into motor vehicles.

11. The mobile device according to claim 1, wherein: The mobile device includes one of a phone, a tablet computer, a laptop computer, and a smart watch.

12. The mobile device according to claim 1, wherein: The product is fuel and the product dispenser is a fuel dispenser.

13. The mobile device according to claim 1, wherein: The product is one of consumables, and the consumables include one of drinking liquid, electricity, air, lottery tickets and food.

14. A method of using a product dispenser, comprising: receiving, at the product dispenser via the wireless communication link, a request from the mobile device to establish a secure connection between the product dispenser and the mobile device; responsive to receiving the request to establish a secure connection, transmitting identification data uniquely identifying the product dispenser to the mobile device; receiving, from the mobile device via the wireless communication link, a security key for secure communications between the product dispenser and the mobile device upon receiving the request to establish a secure connection; establishing a secure connection between the product dispenser and the mobile device, wherein the secure connection allows communication between the product dispenser and the mobile device using a security key; and In response to receiving an authorized payment amount for the product from the mobile device, the product is caused to be dispensed from the product dispenser, wherein the authorized payment amount is encrypted using the security key.

15. The method according to claim 14, wherein: The security key is received by the product dispenser regardless of whether the product dispenser has established a connection with the network cloud server.

16. The method of claim 14, further comprising transmitting status data indicative of a current status of the product dispenser from the product dispenser to the mobile device via the established secure connection.

Images