DESC:EARLIEST PRIORITY DATE:
This Application claims priority from a Provisional patent application filed in India having Patent Application No. 202441070949, filed on September 19, 2024, and titled “A SYSTEM AND A METHOD FOR SEAMLESS POS AND FUEL DISPENSER INTEGRATION FOR ACCURATE PAYMENTS”.
FIELD OF INVENTION
[0001] The present invention relates to the field of automated retail transaction systems. More particularly, the present invention relates to a system and a method for real-time fuel transaction management.
BACKGROUND
[0002] A point-of-sale (POS) system is a critical tool for managing the operations of modern businesses. In the evolving landscape of digital payments, POS integration has become present across industries. Specifically, integrating POS systems with fuel dispensing units has the potential to significantly streamline the payment process, where transaction speed is a crucial factor. For most customers, fuel filling is a routine task that needs to be completed quickly and efficiently.
[0003] However, in traditional systems, once fuelling is complete, customers are presented with a list of fuelling transactions at the POS unit, from which they must manually select the transaction corresponding to their dispenser. This process is often cumbersome, error-prone, and inefficient, especially during peak hours or in high-traffic fuel stations. These challenges largely stem from a lack of real-time connectivity between fuel dispensers and POS systems, resulting in limited data visibility and delays in transaction matching.
[0004] Hence, there is a need for an improved system and a method for real-time fuel transaction management. to address the aforementioned issue(s).
OBJECTIVES OF THE INVENTION
[0005] The primary objective of the invention is to implement a system that automates the fuel transaction process by enabling real-time logging, transmission, and retrieval of fuelling transaction data directly from a fuel dispenser to a point-of-sale unit (POS).
[0006] Another objective of the invention is to enable automatic identification and matching of transactions through proximity-based detection, the system automatically identifies the fuel dispenser used by a customer and matches it with the corresponding transaction from a live queue.
[0007] Yet another objective of the invention is to provide real-time payment processing and receipt generation instantly after fuelling, while updating both the dispensing unit and a central server with the payment confirmation.
SUMMARY
[0008] In accordance with an embodiment of the present disclosure, a system for real-time fuel transaction management is disclosed. The system includes a plurality of fuel dispensing units located at a retail fuel outlet. The plurality of fuel dispensing units is adapted to initiate a fuel dispensing session to a vehicle upon activation by a user. The system includes a point-of-sale unit positioned in proximity to the plurality of fuel dispensing units within the retail fuel outlet. The system includes a processor, and a memory coupled to the processor. The memory comprises instructions that when executed by the processor cause the processor to log fuelling transaction data upon dispensing fuel to the vehicle. The fuelling transaction data is associated with a unique transaction identifier that links a transaction to a specific fuel dispensing unit. Further the processor is caused to transmit the fuelling transaction data in real-time over a wireless network to a server. The server maintains a live queue of ongoing transaction and completed transaction corresponding to the fuelling transaction data. The processor is caused to identify a fuel dispensing unit associated with a user interaction using a short-range communication protocol, based on physical proximity to the point-of-sale unit at the time of transaction initiation. The processor is caused to identify and retrieve the corresponding fuelling transaction data from the live transaction queue stored on the server, based on the identified fuel dispensing unit. The processor is caused to display the fuelling transaction data to the user to verify or cancel transaction prior to initiating a payment. The processor is caused to process the payment based on the fuelling transaction data. The processor is caused to update the payment confirmation to the associated fuel dispensing unit and the server. The processor is caused to generate a receipt for the user upon successful payment.
[0009] In accordance with an embodiment of the present disclosure a method for real-time fuel transaction management is disclosed. The method includes initiating, a fuel dispensing session to a vehicle upon activation by a user. The method includes logging fuelling transaction data upon dispensing fuel to the vehicle. The fuelling transaction data is associated with a unique transaction identifier that links a transaction to a specific fuel dispensing unit. The method includes transmitting the fuelling transaction data in real-time over a wireless network to a server. The server maintains a live queue of ongoing transaction and completed transaction corresponding to the fuelling transaction data. The method includes identifying a fuel dispensing unit associated with a user interaction using a short-range communication protocol, based on physical proximity to the point-of-sale unit at the time of transaction initiation. The method includes identifying and retrieving the corresponding fuelling transaction data from the live transaction queue stored on the server, based on the identified fuel dispensing unit. The method includes displaying the fuelling transaction data to the user to verify or cancel transaction prior to initiating a payment. The method includes processing the payment based on the fuelling transaction data. The method includes updating the payment confirmation to the associated fuel dispensing unit and the server. The method includes generating a receipt for the user upon successful payment.
[0010] To further clarify the advantages and features of the present disclosure, a more particular description of the disclosure will follow by reference to specific embodiments thereof, which are illustrated in the appended figures. It is to be appreciated that these figures depict only typical embodiments of the disclosure and are therefore not to be considered limiting in scope. The disclosure will be described and explained with additional specificity and detail with the appended figures.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The disclosure will be described and explained with additional specificity and detail with the accompanying figures in which:
[0012] FIG. 1 illustrates a network environment for implementing example techniques of a system for real-time fuel transaction management in accordance with an embodiment of the present disclosure;
[0013] FIG. 2 illustrates a schematic diagram of a point-of-sale unit of FIG. 1, in accordance with an example implementation of the present subject matter;
[0014] FIG. 3 illustrates a schematic diagram of a system for real-time fuel transaction management FIG. 1, in accordance with an embodiment of the present disclosure;
[0015] FIG. 4(a) is a flow chart representing the steps involved in a method for real-time fuel transaction management, in accordance with an embodiment of the present disclosure; and
[0016] FIG. 4(b) illustrates continued steps of the method of FIG. 4(a) in accordance with an embodiment of the present disclosure.
[0017] Further, those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the embodiments of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

DETAILED DESCRIPTION
[0018] For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the embodiment illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.
[0019] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or subsystems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an embodiment", "in another embodiment" and similar language throughout this specification may, but not necessarily do, all refer to the same embodiment.
[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.
[0021] In the following specification and the claims, reference will be made to a number of terms, which shall be defined to have the following meanings. The singular forms “a”, “an”, and “the” include plural references unless the context clearly dictates otherwise.
[0022] FIG. 1 illustrates a network environment (100) for implementing example techniques of a system (102) for real-time fuel transaction management in accordance with an embodiment of the present disclosure. Referring to FIG. 1, a plurality of fuel dispensing units (104) located at a retail fuel outlet. The plurality of fuel dispensing units (104) is adapted to initiate a fuel dispensing session to a vehicle upon activation by a user (106). The user (106) is either a customer at a self-service retail fuel outlet or an operator performing the refuelling on behalf of the customer. The fuel dispensing session refers to a sequence of actions performed by the user (106), which may include lifting the nozzle from the fuel dispensing unit (104), entering fuel transaction information, and dispensing fuel to the vehicle by actuating the nozzle.
[0023] Further, the user (106) is communicating to the system (102) through a user interface available at the plurality of fuel dispensing units (104). A user interface may receive input from the user (106) via a display screen, physical buttons, a touchscreen, and the like. The plurality of fuel dispensing units (104) communicatively coupled to the system (102), over a network (108). The network (108) may be a single communication network or a combination of multiple communication networks and may use a variety of different communication protocols. The personalized network (108) may be a wireless network, a wired network, or a combination thereof. Examples of such individual personalized networks include, but are not limited to, Global System for Mobile Communication (GSM) network, Universal Mobile Telecommunications System (UMTS) network, Personal Communications Service (PCS) network, Time Division Multiple Access TDMA) network, Code Division Multiple Access (CDMA) network, Next Generation Network (NON), Public Switched Telephone Network (PSTN). Depending on the technology, the personalized network (106) may include various network entities, such as gateways and routers; however, such details have been omitted for the sake of brevity of the present description.
[0024] In addition, a Point-of-Sale (POS) unit (110) may be positioned in proximity to the plurality of fuel dispensing units (104) within the retail fuel outlet. The POS unit (110) is a dedicated hardware system that user interaction for managing and processing fuelling transactions. The POS unit (110) is configured to receive fuelling transaction data, display transaction information to the user (106) for review, and initiate payment processing. In some embodiments, the POS unit (110) may further support features such as inventory management, sales analytics, loyalty point integration, and real-time transaction synchronization with a server. The POS unit (110) may accept various forms of payment including magnetic stripe cards, digital wallets, QR code-based payments, contactless Near Field Communication (NFC) methods, and the like. The POS unit (110) may be implemented as one of several types, including but not limited to Standalone Terminals, Semi-integrated Terminals, and Fully Integrated Systems. The hardware components of the POS unit (110) may include, but are not limited to, a barcode scanner, touchscreen or display unit, receipt printer, POS terminal, a cash drawer, and the like.
[0025] In accordance with an embodiment of the present disclosure, a system (102) for real-time fuel transaction management is provided. The system (102) comprises a processor and a machine-readable storage medium comprising instructions that, when executed by the processor, cause the processor to log fuelling transaction data upon dispensing fuel to the vehicle. The fuelling transaction data is associated with a unique transaction identifier that links a transaction to a specific fuel dispensing unit (104). The processor is configured to transmit the fuelling transaction data in real-time over a wireless network (108) to a server (112). The server (112) maintains a live queue of ongoing transaction and completed transaction corresponding to the fuelling transaction data. The processor is configured to identify the fuel dispensing unit (104) associated with a user interaction using a short-range communication protocol, based on physical proximity to the point-of-sale unit (110) at the time of transaction initiation. The processor is configured to identify and retrieve the corresponding fuelling transaction data from the live transaction queue stored on the server (112), based on the identified fuel dispensing unit. The processor is configured to display the fuelling transaction data to the user to verify, or cancel transaction prior to initiating a payment. The processor is configured to process the payment based on the fuelling transaction data. The processor is configured to update the payment confirmation to the associated fuel dispensing unit (104) and the server (112). The processor, cause the processor to generate a receipt for the user upon successful payment.
[0026] It may be noted that the foregoing system is an exemplary system and may be implemented as computer executable instructions in any computing or processing environment, including in digital electronic circuitry or in computer hardware, firmware, device driver, or software. As such, the system is not limited to any specific hardware or software configuration.
[0001] FIG. 2 illustrates a schematic diagram of a point-of-sale unit (110), in accordance with an example implementation of the present subject matter. Referring to FIG. 2, the point-of-sale unit (110) may comprise a processor(s) (120), a memory(s) (122) coupled to and accessible by the processor(s) (120), and an interface coupled to the memory(s) (122). The point-of-sale unit (110) disclosed herein may be same as the point-of-sale unit (110) described in FIG. 1. The functions of various elements shown in the figs., including any functional blocks labelled as "processor(s)", may be provided through the use of dedicated hardware as well as hardware capable of executing instructions. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, explicit use of the term "processor" would not be construed to refer exclusively to hardware capable of executing instructions, and may implicitly comprise, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA). Other hardware, standard and/or custom, may also be coupled to the processor(s). The point-of-sale unit (110) may further include a display (124) in addition to other components such as, but not limited to, keyboard, sensors, logic circuits etc. Further, the point-of-sale unit (110) may include data (126) that may be stored, utilized or generated during the operation of the point-of-sale unit (110).
[0002] The memory(s) (122) may be a computer-readable medium, examples of which comprise volatile memory (e.g., RAM), and/or non-volatile memory (e.g., Erasable Programmable read-only memory, i.e. EPROM, flash memory, etc.). The memory(s) (122) may be an external memory, or internal memory, such as a flash drive, a compact disk drive, an external hard disk drive, or the like. The point-of-sale unit (110) may further include an interface (128) that may allow the connection or coupling of the point-of-sale unit (110) with one or more other devices, through a wired (e.g., Local Area Network, i.e., LAN) connection or through a wireless connection (e.g., Bluetooth®, Wi-Fi), for example, for connecting to the system shown in FIG. 1. The interface (128) may also enable intercommunication between different logical as well as hardware components of the point-of-sale unit (110).
[0027] FIG. 3 illustrates a schematic diagram of a system (102) for real-time fuel transaction management FIG. 1, in accordance with an embodiment of the present disclosure. Referring to FIG. 3, the system (102) includes a processor(s) (200), a memory(s) (205) coupled to and accessible by the processor(s) (200), a database (215) and a user interface (220) coupled to the memory(s) (205).
[0028] The system (102) disclosed herein is the same as the system (102) described in FIG. 1. The functions of various elements shown in the figs., including any functional blocks labelled as "processor(s)", may be provided through the use of dedicated hardware as well as hardware capable of executing instructions. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, explicit use of the term "processor" would not be construed to refer exclusively to hardware capable of executing instructions, and may implicitly comprise, without limitation, digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA). Other hardware, standard and/or custom, may also be coupled to the processor(s) (200). The system (102) may further include other components such as, but not limited to, keyboard, sensors, logic circuits, input/output interfaces etc. Further, the system (102) may include data (210) which may include data that may be stored, utilized or generated during the operation of the computer implemented system (102).
[0029] The memory(s) (205) may be a computer-readable medium, examples of which comprise volatile memory (e.g., RAM), and/or non-volatile memory (e.g., Erasable Programmable read-only memory, i.e. EPROM, flash memory, etc.). The memory(s) (205) may be an external memory, or internal memory, such as a flash drive, a compact disk drive, an external hard disk drive, or the like. The system (102) may further include the user interface (220) that may allow the connection or coupling of the system (102) with one or more other devices, through a wired (e.g., Local Area Network, i.e., LAN) connection or through a wireless connection (e.g., Bluetooth®, Wi-Fi). The user interface (220) may also enable intercommunication between different logical as well as hardware components of the system (102).
[0030] The system (102) may be provided with the database (215) to store fuelling transaction data refers to information captured during the fuel dispensing session from a plurality of fuel dispensing unit. The fuelling transaction data includes but are not limited to at least one of the unique transaction identifier, the fuel type, the fuel volume, the transaction cost, and the like. In an example implementation of the system (102) including one or more servers, the databases may databases local to the server or may be remote to the server. It may be noted that the data in the databases may be stored as a table or may be pre-stored as a mapping with the other. This application is not limited thereto.
[0031] The system (102) may include module(s). The module(s) may include a user interface module (225), a transaction logging module (230), a communication module (235), a proximity detection module (240), a retrieval module (245), a display module (250) and a payment processing module (255). In one example, the module(s) may be implemented as a combination of hardware and firmware. In an example described herein, such combinations of hardware and firmware may be implemented in several different ways. For example, the firmware for module(s) may be processor (200) executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the module(s) may include a processing resource (for example, implemented as either single processor or combination of multiple processors), to execute such instructions. Further, the hardware for the module(s) may include communication apparatuses, control circuitries involving electrical and electronics components, sensors, and interface devices, which may be in communication with each other for multi-directional communication therebetween.
[0001] Further, the system includes data (210). The data (210) may either be stored or generated as a result of functions implemented by the system. It may be further noted that information stored and available in data may be utilized by the system for performing various functions by the system. In an example, data (210) may include fuelling transaction data (260). It may be noted that such examples of the various functions are only indicative. The present approaches may be applicable to other examples without deviating from the scope of the present subject matter.
[0002] In the present examples, the non-transitory machine-readable storage medium may store instructions that, when executed by the processing resource, implement the functionalities of modules(s). In such examples, the system (102) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions. In other examples of the present subject matter, the machine-readable storage medium may be located at a different location but accessible to the system (102) and the processor(s) (200).
[0003] In operation, a user interface module (225) receives fuelling information as input from a user, after which a transaction logging module (230) log fuelling transaction data upon dispensing fuel to the vehicle by a fuel dispensing unit. The fuelling transaction data refers to information captured during the fuel dispensing session from a plurality of fuel dispensing unit. The fuelling transaction data includes, but is not limited to, at least one of: a unique transaction identifier, fuel type, fuel volume, transaction cost, and the like.
[0004] The user interface module (225) allows the user to input or select the fuelling information, such as fuel type, and fuel volume desired. The user interface module (225) may receive input through, but is not limited to, a display screen, physical buttons, a touchscreen, and the like. Additionally, the user interface module (225) may display a transaction cost based on selected fuel type and volume.
[0005] More specifically, upon receiving the fuel information input from the user, the transaction logging module (230) logs the corresponding fuelling transaction data when fuel is dispensed to the vehicle. The logged fuelling transaction data is associated with the unique transaction identifier that links the transaction to the fuel dispensing unit used.
[0006] A communication module (235) is configured to transmit the fuelling transaction data in real-time over a wireless network to a server. Examples for the wireless network includes but are not limited to Wi-Fi, Zigbee, Narrowband Internet of Things (NB-IoT), and the like.
[0007] In a specific embodiment, the wireless network includes a low-power wide-area network (LPWAN), such as Long-Range Wide Area Network (LoRaWAN), selected for its low power consumption, long-range communication capability, and suitability for connecting fuel dispensers distributed across a large retail fuel outlet. The server maintains a live queue of ongoing transaction and completed transaction corresponding to the fuelling transaction data. The use of LoRaWAN technology ensures that all transaction data is reliably transmitted in real-time, thereby maintaining a continuously updated live queue of ongoing and completed transactions.
[0008] In one embodiment, the server may include a cloud-based server. In another embodiment, parts of the server may be a local server coupled to plurality of fuel dispensing units and a point-of-sale unit.
[0009] Further, a proximity detection module (240) of the point-of-sale unit is operatively coupled to the communication module (235). The proximity is configured to identify a fuel dispensing unit associated with a user interaction using a short-range communication protocol, based on physical proximity to the point-of-sale unit at the time of transaction initiation. The short-range communication protocol includes but are not limited to at least one of Bluetooth communication, near-field communication, radio-frequency identification and the like. More specifically, the POS unit and each fuel dispensing unit are equipped with the short-range communication protocol. After the fuelling session is completed, when the user walks toward the POS unit to make a payment, the proximity detection module (240) detects the nearest fuel dispensing unit based on signal strength or proximity.
[0010] In an embodiment, the POS unit may further include a proximity sensor to enhance the accuracy of detecting the correct dispensing unit associated with the user.
[0011] A retrieval module (245) is operatively coupled to the proximity detection module (240). The retrieval module (245) is configured to identify and retrieve the corresponding fuelling transaction data from the live transaction queue stored on the server, based on the identified fuel dispensing unit.
[0012] A display module (250) operatively coupled to the retrieval module (245). The display module (250) is configured to display the fuelling transaction data to the user to verify or cancel transaction prior to initiating a payment through a user interface. More specifically, the fuelling transaction data is displayed to the user, and only upon confirmation is the payment process initiated. The display may occur through one or more output means, including but not limited to a graphical user interface (GUI), visual display screen, and the like.
[0013] In an embodiment, the point-of-sale unit comprises an audio interface configured to deliver a voice-based output of the fuelling transaction data for user interaction, thereby facilitating improved accessibility.
[0014] A payment processing module (255) is operatively coupled to the display module (250). The payment processing module (255) is configured to facilitate selection of a payment method by the user upon successful verification. Examples of the payment method includes but are not limited to credit cards, debit cards, third-party payment gateways (e.g., Apple Pay, Google Pay, and the like), Unified Payments Interface (UPI) systems, and the like. The user may select one of the payment methods after successful verification.
[0015] Further, the payment processing module (255) is configured to process the payment based on the fuelling transaction data. Further, the payment processing module (255) is configured to update the payment confirmation to the associated fuel dispensing unit and the server. The payment processing module (255) is configured to generate a receipt for the user upon successful payment though the POS terminal. The receipt may include the fuel transaction data, along with timestamp, payment mode, and the like.
[0016] In an embodiment, the receipt may be physical (via printer) or digital (via SMS, email, app notification, etc).
[0017] In an embodiment, the payment processing module (255) is configured to log the receipt into a central repository on the server for post-transaction audit and record-keeping. The logged data may include, but is not limited to, the unique transaction identifier, timestamp, payment method, the fuel transaction data, receipt delivery method, and the like.
[0018] Let’s consider an example where a user “X” arrives at a retail fuel outlet who uses the system for real-time fuel transaction management described in the present invention. In this scenario, the fuel dispensing operation is managed by an operator. The user “X” drives up to one of the available fuel dispensing units. The operator at the fuel dispensing unit interacts with the user interface module (225) integrated into the dispensing unit. Through a display screen the operator enters the necessary fuelling transaction information such as the selected fuel type (e.g., diesel or petrol) and the desired fuel volume or desired fuel cost. Once the operator begins dispensing fuel, the transaction logging module (230) of the dispensing unit automatically logs all fuelling transaction data in real-time. This data includes, but is not limited to the unique transaction identifier, fuel type, fuel volume, transaction cost, and the like. Simultaneously, the communication module (235) which is operatively coupled to the transaction logging module, transmits the fuelling transaction data wirelessly to the Point-of-Sale (POS) unit using a Long-Range Wide Area Network (LoRaWAN) communication protocol. At the POS unit, the proximity detection module (240) determines the closest fuel dispensing unit in relation to the operator in which the last dispensing is being done, using short-range communication such as Bluetooth Low Energy. The retrieval module (245) within the POS unit queries the live transaction queue maintained by the central server, identifies the corresponding transaction identifier and retrieves the associated fuelling transaction data. The fuelling transaction data is further displayed via the display module (250) on the POS unit, allowing the user “X” to verify or cancel the transaction before proceeding to payment.
[0019] Once the transaction is confirmed by the user “X”, the payment processing module (255) processes the payment using a preferred payment. Upon successful payment, a payment confirmation is sent to both the POS unit and the fuel dispensing unit. The receipt is generated for the customer in printed form.
[0020] FIG. 4(a) is a flow chart representing the steps involved in a method (400) for real-time fuel transaction management, in accordance with an embodiment of the present disclosure. FIG. 4(b) illustrates continued steps of the method (400) of FIG. 4(a) in accordance with an embodiment of the present disclosure. The method (400) includes initiating, a fuel dispensing session to a vehicle upon activation by a user in step 405. The fuel dispensing session refers to a sequence of actions performed by the user, which may include lifting the nozzle from a fuel dispensing unit, entering fuel transaction information, and dispensing fuel to the vehicle by actuating the nozzle.
[0021] In an embodiment, each fuel dispensing unit comprises a user interface module configured to allow the user to input or select fuelling information, such as fuel type, and fuel volume desired. The user interface module may receive input through, but is not limited to, a display screen, physical buttons, a touchscreen, and the like. Additionally, the user interface module may display a transaction cost based on selected fuel type and volume.
[0022] The method (400) includes logging fuelling transaction data upon dispensing fuel to the vehicle. The fuelling transaction data is associated with a unique transaction identifier that links a transaction to a specific fuel dispensing unit in step 410. The fuelling transaction data refers to information captured during the fuel dispensing session. The fuelling transaction data includes but are not limited to at least one of the unique transaction identifier, the fuel type, the fuel volume, the transaction cost, and the like.
[0032] The method (400) includes transmitting the fuelling transaction data in real-time over a wireless network to a server. The server maintains a live queue of ongoing transaction and completed transaction corresponding to the fuelling transaction data in step 415. Examples for the wireless network includes but are not limited to Wi-Fi, Zigbee, Narrowband Internet of Things (NB-IoT), and the like.
[0033] In a specific embodiment, the wireless network includes a low-power wide-area network (LPWAN), such as Long-Range Wide Area Network (LoRaWAN), selected for its low power consumption, long-range communication capability, and suitability for connecting fuel dispensers distributed across a large retail fuel outlet. The server maintains a live queue of ongoing transaction and completed transaction corresponding to the fuelling transaction data. The use of LoRaWAN technology ensures that all transaction data is reliably transmitted in real-time, thereby maintaining a continuously updated live queue of ongoing and completed transactions.
[0023] The method (400) includes identifying a fuel dispensing unit associated with a user interaction using a short-range communication protocol, based on physical proximity to a point-of-sale unit at the time of transaction initiation in step 420. The short-range communication protocol includes but are not limited to at least one of Bluetooth communication, near-field communication, radio-frequency identification and the like. More specifically, the POS unit and each fuel dispensing unit are equipped with the short-range communication protocol. After the fuelling session is completed, when the user walks toward the POS unit to make a payment, the proximity detection module detects the nearest fuel dispensing unit based on signal strength or proximity.
[0034] The method (400) includes identifying and retrieving the corresponding fuelling transaction data from the live transaction queue stored on the server, based on the identified fuel dispensing unit in step 425.
[0035] The method (400) includes displaying the fuelling transaction data to the user to verify or cancel transaction prior to initiating a payment in step 430. More specifically, the fuelling transaction data is displayed to the user, and only upon confirmation is the payment process initiated.
[0036] The method (400) includes processing the payment based on the fuelling transaction data in step 435.
[0037] The method (400) includes updating the payment confirmation to the associated fuel dispensing unit and the server in step 440.
[0038] The method (400) includes generating a receipt for the user upon successful payment in step 445.
[0039] In an embodiment, the receipt may be physical (via printer) or digital (via SMS, email, app notification, etc).
[0040] In an embodiment, the method (400) includes logging the receipt into a central repository on the server for post-transaction audit and record-keeping.
[0041] Thus, various embodiments of the system and method for real-time fuel transaction management provides several benefits. The system enables real-time capture and transmission of the fuelling transaction data, ensuring timely and accurate processing. By integrating proximity-based detection such as Bluetooth, NFC, or proximity sensors, the system automatically identifies the specific dispensing unit associated with the user, eliminating manual errors and enhancing transaction accuracy. Further, this automated matching significantly reduces customer wait times and simplifies the payment process, resulting in an efficient user experience. The use of wireless network such as LoRaWAN, the system ensures scalability and reliability across large retail outlets with multiple dispensing units. It can easily be adapted to different sizes and configurations of fuel stations, making it a versatile solution for varying retail environments. Additionally, the system supports secure, multi-mode payment options and improved customer satisfaction. Further, the integration of real-time communication and proximity detection ensures that the checkout process is both quick and accurate, leading to higher customer satisfaction and turnover.
[0042] The techniques described in this disclosure may be implemented, at least in part, in hardware, software, firmware, or any combination thereof. For example, various aspects of the described techniques may be implemented within one or more processors, including one or more microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or any other equivalent integrated or discrete logic circuitry, as well as any combinations of such components. The term “processor” or “processing subsystem” may generally refer to any of the foregoing logic circuitry, alone or in combination with other logic circuitry, or any other equivalent circuitry. A control unit including hardware may also perform one or more of the techniques of this disclosure.
[0043] Such hardware, software, and firmware may be implemented within the same device or within separate devices to support the various techniques described in this disclosure. In addition, any of the described units, modules, or components may be implemented together or separately as discrete but interoperable logic devices. Depiction of different features as modules or units is intended to highlight different functional aspects and does not necessarily imply that such modules or units must be realized by separate hardware, firmware, or software components. Rather, functionality associated with one or more modules or units may be performed by separate hardware, firmware, or software components, or integrated within common or separate hardware, firmware, or software components.
[0044] It will be understood by those skilled in the art that the foregoing general description and the following detailed description are exemplary and explanatory of the disclosure and are not intended to be restrictive thereof.
[0045] While specific language has been used to describe the disclosure, any limitations arising on account of the same are not intended. As would be apparent to a person skilled in the art, various working modifications may be made to the method in order to implement the inventive concept as taught herein.
[0046] The figures and the foregoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, the order of processes described herein may be changed and are not limited to the manner described herein. Moreover, the actions of any flow diagram need not be implemented in the order shown; nor do all of the acts need to be necessarily performed. Also, those acts that are not dependent on other acts may be performed in parallel with the other acts. The scope of embodiments is by no means limited by these specific examples.
,CLAIMS:WE CLAIM:
1. A system for real-time fuel transaction management, comprising:
a plurality of fuel dispensing units located at a retail fuel outlet, wherein the plurality of fuel dispensing units is adapted to initiate a fuel dispensing session to a vehicle upon activation by a user;
a point-of-sale unit positioned in proximity to the plurality of fuel dispensing units within the retail fuel outlet;
a processor; and
a memory coupled to the processor, wherein the memory comprises instructions that when executed by the processor cause the processor to:
log fuelling transaction data upon dispensing fuel to the vehicle, wherein the fuelling transaction data is associated with a unique transaction identifier that links a transaction to a specific fuel dispensing unit;
transmit the fuelling transaction data in real-time over a wireless network to a server, wherein the server maintains a live queue of ongoing transaction and completed transaction corresponding to the fuelling transaction data;
identify a fuel dispensing unit associated with a user interaction using a short-range communication protocol, based on physical proximity to the point-of-sale unit at the time of transaction initiation;
identify and retrieve the corresponding fuelling transaction data from the live transaction queue stored on the server, based on the identified fuel dispensing unit;
display the fuelling transaction data to the user to verify, or cancel transaction prior to initiating a payment;
process the payment based on the fuelling transaction data;
update the payment confirmation to the associated fuel dispensing unit and the server; and
generate a receipt for the user upon successful payment.

2. The system as claimed in claim 1, wherein the fuelling transaction data comprises at least the unique transaction identifier, fuel type, fuel volume, and transaction cost.

3. The system as claimed in claim 1, wherein the wireless network comprises a low-power wide-area network based on long-range wide-area network communication.

4. The system as claimed in claim 1, wherein the short-range communication protocol comprises at least one of Bluetooth communication, near-field communication, and radio-frequency identification.

5. The system as claimed in claim 1, to cause the processor to allow the user to input or select fuelling information from the user.

6. The system as claimed in claim 1, to cause the processor to facilitate selection of a payment method by the user upon successful verification.

7. The system as claimed in claim 1, to cause the processor to log the receipt into a central repository on the server for post-transaction audit and record-keeping.

8. A method for real-time fuel transaction management, comprising:
initiating, a fuel dispensing session to a vehicle upon activation by a user;
logging fuelling transaction data upon dispensing fuel to the vehicle, wherein the fuelling transaction data is associated with a unique transaction identifier that links a transaction to a specific fuel dispensing unit;
transmitting the fuelling transaction data in real-time over a wireless network to a server, wherein the server maintains a live queue of ongoing transaction and completed transaction corresponding to the fuelling transaction data;
identifying a fuel dispensing unit associated with a user interaction using a short-range communication protocol, based on physical proximity to the point-of-sale unit at the time of transaction initiation;
identifying and retrieving the corresponding fuelling transaction data from the live transaction queue stored on the server, based on the identified fuel dispensing unit;
displaying the fuelling transaction data to the user to verify, or cancel transaction prior to initiating a payment;
processing the payment based on the fuelling transaction data;
updating the payment confirmation to the associated fuel dispensing unit and the server; and
generating a receipt for the user upon successful payment.

Dated this 06th day of August 2025

Signature

Prakriti Bhattacharya
Patent Agent (IN/PA-5178)
Agent for applicant