System, device, and method of digital payment for refueling vehicles

Abstract

A system for refueling vehicles may include an application installed in a mobile device, configured to: instruct a user to insert a refueling gun of a fuel pump into a fuel tank inlet of a vehicle; instruct the user to place the mobile device within a wireless communication range of an identification device attached to the vehicle in the vicinity of the fuel tank inlet, wherein the identification device comprises a sensor configured to detect the presence of the refueling gun in the fuel tank inlet; receive from the identification device a unique identification (UID) of the vehicle and a confirmation of presence the refueling gun in the fuel tank inlet via a near field communication (NFC) component in the mobile device; report to the management server that the refueling gun is in the fuel tank inlet associated with the UID; receive from the management server a unique identifier of a single-use virtual payment card for use in a refueling transaction at the service station according to a refueling policy set in the management server for the UID; and request, via the NFC component in the mobile device in communication with a payment terminal at the service station, approval of the refueling transaction.

Description

SYSTEM, DEVICE, AND METHOD OF DIGITAL PAYMENT FOR REFUELING VEHICLESTECHNICAL FIELD

[0001] The present disclosure relates generally to digital payment systems for refueling vehicles and, more particularly, to a refueling system that employs advanced sensor technology, mobile communication, and digital payment methods to streamline and secure the process of vehicle refueling.BACKGROUND

[0002] The conventional method of refueling a vehicle involves the manual insertion of a pump gun into a vehicle's refueling nozzle, followed by payment either through a cash or a card. This method, while commonplace, has several disadvantages which are, for example, a physical presence of the user for the entire refueling process is required, exposes a user's payment information to potential fraud, and it is lacks a comprehensive system to monitor and control the refueling process.

[0003] Furthermore, conventional refueling systems do not provide a secure and efficient method of customer identification. This lack of proper identification methods can lead to fraudulent activities such as unauthorized refueling. Also, traditional systems do not have a method to monitor the connection between the refueling gun and the fuel tank inlet, which can lead to fuel wastage.

[0004] Additionally, the current payment methods in conventional refueling systems are not as secure as they could be. The use of physical credit or debit cards exposes users to the risk of their sensitive payment information being stolen.

[0005] In light of the above-described disadvantages, there is a need for a more secure, efficient, and user-friendly refueling system.

[0006] The present invention aims to address these drawbacks by introducing a system that leverages digital payment methods, advanced sensor technology, and mobile communication. This system not only makes the refueling process more efficient and secure but also provides additional advantages over existing methods, asdetailed in the following chapter.

[0007] The advent of digital payment systems has revolutionized the way transactions are carried out in various sectors, including online shopping, bill payments, and other services. These systems typically involve the use of a user's credit card or other payment methods such as PayPal, cryptocurrency, and the like to pay for goods or services. However, these systems are not without their limitations, particularly when it comes to vehicle-related services such as, for example, fueling at a gas station or charging an electric vehicle at a charging station.

[0008] One of the main disadvantages of existing digital payment systems is the risk of unauthorized usage. For instance, a company's digital or physical payment card may be used privately for fueling a vehicle or charging an electric vehicle without authorization. This unauthorized use of payment cards can result in significant financial losses for companies and can also lead to fraudulent activities.

[0009] Moreover, traditional payment methods at service stations often require manual input of vehicle information or payment details, which can be time-consuming and prone to errors. Additionally, these methods do not provide real-time monitoring of the fueling process, which can lead to overcharging or undercharging of the service.

[0010] More advance payment methods at service stations may include means for automatically identifying a vehicle before authorizing refueling. Some of these systems employ a vehicle identifier such as an RFID tag or scannable code (i.e. QR code or barcode), however, identifying a vehicle to activate refueling with this kind of systems allows users to abuse of the payment method by refueling other unauthorized vehicles or containers after identifying the authorized vehicle, which is a situation that companies want to avoid when they provide a payment method to their employee for the purpose of refueling a specific vehicle they are using for their work.

[0011] Other systems may resolve this by using a communication device on a refueling gun at the service station which identifies a vehicle through an identification device on the vehicle’s refueling inlet. While this kind of systems may prevent refueling when the refueling gun is removed from the authorized vehicle’s refueling inlet, they require costly upgrade of the fuel pumps to allow them to communicate with the identification devices on the vehicles.

[0012] Therefore, there is a need for a system to overcome the above described disadvantages.GENERAL DESCRIPTION

[0013] The following presents a simplified summary of various aspects described herein. This summary is not an extensive overview and is not intended to identify required or critical elements or to delineate the scope of the claims. The following summary merely presents some concepts in a simplified form as an introductory prelude to the more detailed description provided below.

[0014] According to aspects described herein, embodiments related to a system and a method for paying for fueling and buying services and goods, for example, at a gas station, are described below by the ways of example only.

[0015] A preferred embodiment of the present invention includes a system for refueling a vehicle (105) at a service station performed by an application (125) installed in a mobile device (101), configured to: instruct a user to insert a refueling gun (116) of a fuel pump (114) into a fuel tank inlet (118) of the vehicle (105); instruct the user to place the mobile device within a wireless communication range of an identification device attached to the vehicle in the vicinity of the fuel tank inlet (118), wherein the identification device comprises a sensor which is configured to detect the presence of the refueling gun (116) in the fuel tank inlet (118); receive from the identification device a unique identification (UTD) of the vehicle (105) and a confirmation of presence the refueling gun (116) in the fuel tank inlet (118) via a near field communication (NFC) component in the mobile device (101); report to the management server (106) that the refueling gun (116) is in the fuel tank inlet (118) associated with the UTD; receive (104) from the management server (106) a unique identifier of a single-use virtual payment card (120) for use in a refueling transaction at the service station according to a refueling policy set in the management server for the UID; and request, via the NFC component in the mobile device in communication with a payment terminal (108) at the service station, approval of the refueling transaction.

[0016] This system allows a user to perform a secure refueling of their vehicle at any service station with an EMV payment terminal through the user’s mobile device, without requiring replacement of the gas pumps or refueling guns or installing any devices on them that would allow them to communicate with the identification deviceon the vehicle. The identification device on the vehicle’s fuel tank inlet, which functions both as a unique identifier of the vehicle and a detector of insertion of a refueling gun, is in communication with the user’s mobile device via the NFC component in it. This allows to application on the user’s mobile device to report to the management server whether the vehicle identity match the details stored in the server along with the payment method and whether a refueling gun is inserted into the fuel tank inlet. Only when these two conditions are met, the management server issues a single-use virtual payment card valid only for that specific refueling transaction, which the user then uses to pay to activate the gas pump and pay for the refueling transaction at the EMV payment terminal, through the NFC component in the user’ s mobile device.

[0017] In another embodiment, said sensor is configured to continuously monitor presence of the refueling gun (116) in the fuel tank inlet (118), and the mobile device is configured to receive a signal from the identification device (105) in real-time when the refueling gun (116) is removed from the fuel tank inlet (118) and report to the management server.

[0018] In another embodiment, the system is further configured to instruct the fuel pump (114) to stop refueling when the refueling gun (116) is removed from the fuel tank inlet (118).

[0019] In another embodiment, the management server is configured to calculate an overall refueling time between inserting and removing the refueling gun (116) from the fuel tank inlet (118) and assess whether the amount of the refueling transaction is consistent with the overall refueling time; and upon detecting that the overall refueling time is not consistent with the amount of the refueling transaction, flag the transaction as a potentially illegitimate transaction.

[0020] In another embodiment, the management server (106) is configured to load the single-use virtual payment card (120) with a limit corresponding to the amount required to be approved for initiating the refueling transaction.

[0021] In another embodiment, the application in the mobile device is configured to notify the user when the refueling gun (116) is inserted into or removed from the fuel tank inlet (118) associated with the UTD stored in the application for the user.

[0022] In another embodiment, the mobile device is further configured to: instructthe user to place the mobile device (101) within a wireless communication range with a payment terminal (108) for initiating the refueling transaction; receive (110) through the payment terminal (108) an approval of the refueling transaction using the singleuse virtual payment card (120).

[0023] In another embodiment, the approval is based on at least one of: a token usage policy, a user balance, a user payment card limit, a refueling location, a refueling hour, a fuel type.

[0024] In another embodiment, the communication device is configured to: transfer data to the application, wherein the data comprise at least one of: a vehicle type, a vehicle number, a vehicle owner, and a fuel type.

[0025] In another embodiment, the NFC component is a radio frequency identification (RFID) tag.

[0026] In another embodiment, the NFC component is a Bluetooth transmitter.

[0027] In another embodiment, the sensor is configured to detect the presence of the refueling gun by closing a circuit through a conducting part of the refueling gun.

[0028] In another embodiment, the management server is configured to load the single-use virtual payment card (120) with a limit corresponding to an amount of the refueling transaction received from the service station.

[0029] In another embodiment, the management server is configured to change a status of the single-use virtual payment card (120) to cancelled after completion of the refueling transaction.

[0030] In another embodiment, the sensor is configured to detect a specific characteristic of the refueling gun (116), such as its shape, size, or material composition, to distinguish it from other objects placed in the fuel tank inlet (118).

[0031] In another embodiment, the sensor comprises a magnetic field sensor configured to detect the magnetic signature of the refueling gun (116).

[0032] In another embodiment, the sensor comprises an optical sensor configured to detect the presence of the refueling gun (116) based on light reflection or interruption.

[0033] In another embodiment, the sensor is configured to monitor the fuel level in the fuel tank of the vehicle and the mobile device is configured receive a fuel level data from the sensor through the identification device, and to send an instruction to stop the refueling process when the fuel level is in or beyond a predetermined fuel limit.

[0034] In another embodiment, data from the sensor is integrated with date from the fuel pump (114) to provide real-time data on the refueling flow rate.

[0035] In another embodiment, the mobile device is securely paired with the identification device (105) using a unique identifier to prevent unauthorized communication.

[0036] In another embodiment, the system further comprising a temperature sensor integrated with the sensor to monitor a temperature in the area of the fuel tank inlet during refueling and wherein the application on the mobile device is configured to generate an alert when the temperature is exceeding a predetermined temperature threshold.

[0037] In another embodiment, the system further comprising a pressure sensor integrated with the sensor to monitor the pressure in the fuel system during refueling.

[0038] In another embodiment, the sensor is configured to perform periodic checks at predetermined intervals to confirm the continued presence of the refueling gun (116) in the fuel tank inlet (118) during the refueling process.

[0039] In another embodiment, the sensor additionally monitors the fuel level in the vehicle's fuel tank and automatically transmits a signal to the fuel pump (114) to stop refueling when a predetermined fuel level is reached.

[0040] In another embodiment, the sensor analyzes the fuel flow rate and compares it to historical data for the specific vehicle type to detect potential anomalies or overfilling attempts.

[0041] In another embodiment, the sensor is configured to detect flow of fuel from the refueling gun into the fuel tank inlet.

[0042] In another embodiment, the application on the mobile device is configured to monitor the duration of fuel flow into sent from the sensor.

[0043] In another embodiment, the application is configured to generate anotification in at least one of the following: fuel flow time below a predetermined minimum duration, fuel flow time above a predetermined maximum duration.

[0044] In another embodiment, the management server is configured to calculate an overall fuel flow time and assess whether the amount of the refueling transaction is consistent with the overall fuel flow time; and upon detecting that the overall fuel flow time is not consistent with the amount of the refueling transaction, flag the transaction as a potentially illegitimate transaction.

[0045] In another embodiment, the sensor utilizes ultrasonic technology to accurately detect the presence and position of the refueling gun (116) within the fuel tank inlet (118).

[0046] In another embodiment, the sensor employs image recognition to visually identify the type and compatibility of the inserted refueling gun (116).

[0047] In another embodiment, the sensor incorporates radio frequency identification (RFID) technology to uniquely identify the inserted refueling gun (116) and prevent unauthorized use.

[0048] Various objects, features, aspects, and advantages of the present invention will become more apparent from the following detailed description of preferred embodiments of the invention, along with the accompanying drawings in which like numerals represent like components.BRIEF DESCRIPTION OF THE DRAWINGS

[0049] In order to better understand the subject matter that is disclosed herein and to exemplify how it may be carried out in practice, embodiments will now be described, by way of non-limiting example only, with reference to the accompanying drawings, in which:

[0050] Figure 1 illustrates a block diagram of a system for performing payments for fueling and / or charging an authorized vehicle according to some other demonstrative embodiments.

[0051] Figure 2 illustrates a flow chart of a method for performing payments for fueling and / or charging an authorized vehicle according to some other demonstrative embodiments.

[0052] Figure 3 illustrates a block diagram of a system for performing payments for maintenance and / or usage of an authorized vehicle according to some demonstrative embodiments.

[0053] Figure 4 illustrates a flow chart of a method for performing payment for vehicle maintenance and / or usage by a payment application, according to some demonstrative embodiments.

[0054] Figure 5 illustrates a block diagram of a system for performing payments for maintenance and / or usage of an authorized vehicle according to some other demonstrative embodiments.

[0055] Figure 6 illustrates a flow chart of a method for performing payment at a service station with a payment application, according to some other demonstrative embodiments.

[0056] Figure 7 illustrates a block diagram of another system for performing payments for fueling and / or charging an authorized vehicle according to some other demonstrative embodiments.

[0057] Figure 8 illustrates a product of manufacture according to some demonstrative embodimentsDETAILED DESCRIPTION OF THE DRAWINGS

[0058] The present patent application, offers a unique and innovative approach to the refueling process of vehicles. This disclosure primarily revolves around a refueling system that operates according to a new and not obvious algorithm that is configured to establish a link between the pump gun and the refueling nozzle to the final payment for the fuel.

[0059] In some demonstrative embodiments, the user may be instructed via an application's user interface (UI) to insert the refueling gun into the vehicle's refueling inlet. A sensor, which may be placed in the vicinity of the refueling inlet, detects the connection between the refueling gun and the fuel tank inlet. This sensor may be one of, for example, volume sensors, circuit closing detectors, conductivity sensors, electromagnetic field detectors, and / or movement sensors. The sensor may communicate the information to a mobile communication device, e.g., a cell phone, which may report to a server that a connection between the refueling gun and the fuel tank inlet has been established, and the refueling of the vehicle may proceed.

[0060] In some demonstrative embodiments, the method may provide identification (ID) data of a customer, e.g., the user, to the server. For example, the user may be instructed to attach the communication device, e.g., a cell phone, to an identification device, e.g., a sticker, affixed to the vehicle. For example, the identification device may include a Near Field Communication (NFC) transceiver and may provide the ID data of the customer through NFC transmission to the communication device, e.g., the cellphone, using the application, e.g., a fueling application. For example, the application may be loaded with a payment token, such as a single-use virtual payment card, that may include, for example, a credit card number, and a zero balance. The application may be configured to communicate with the server, transfer the token, e.g., the credit card number and unique identification (UTD) from the ID device, e.g., the sticker, and may submit a request for refueling the vehicle. The server may check a payment policy and balance associated with the UTD before approving or rejecting the refueling request.

[0061] In some demonstrative embodiments, the method may provide the identification between a payment system, e.g., Europay, Mastercard, and Visa (EMV)system, a credit card company, and the server. For example, the customer and / or the user may be instructed to link their communication devices, e.g., cell phones, to the EMV system, e.g., a payment terminal, at the gas station, and the payment token or single-use virtual payment card may be transferred to the payment terminal, e.g., an EMV terminal. The payment terminal, EMV terminal, may request the credit company for transaction approval. The server may identify the transaction and verify that the pump gun and the refueling inlet are connected before approving the payment request.

[0062] In some demonstrative embodiments, the method may end after the refueling and payment process. For example, after refueling, the refueling information may be transferred to the credit company, which may charge and report the transaction to the server.

[0063] Advantageously, the use of the above-described system and the method allows a replacement of a fuel platform without necessitating any changes at the service station, e.g., a gas station. Furthermore, it enables the use of the communication device, e.g., the cell phone, as a vehicle identification, communication, payment, and fraud prevention tool during the refueling process and offers a secure payment.

[0064] This chapter elaborates on the innovative system, device, and method of digital payment for vehicle usage, specifically focusing on the refueling process. The invention proposes a novel way of integrating digital payment into the refueling process, significantly enhancing user experience and security.

[0065] The invention's main point is the link between the pump gun and the refueling nozzle, which is checked and monitored throughout the refueling process. In the application user interface (UI), the user is instructed to insert the refueling gun into the vehicle's fuel nozzle. A sensor, which can be attached via a sticker next to the refueling nozzle, detects and reports the connection between the refueling gun and the nozzle to a cell phone. The cell phone then communicates this information to the server, enabling continuous refueling.

[0066] The system incorporates at least one of several possible sensors, including a volume sensor, a sensor that detects the closing of an electrical circuit, a sensor that detects conductivity, a sensor that detects an electromagnetic field, and a sensor that detects movement. If, at any step, the phone reports that the connection has stopped,the server can instruct the credit company to halt the transaction and refueling process.

[0067] The customer and the server are identified through the application. The user is instructed to attach their cell phone to the sticker affixed to the vehicle. The cell phone then pairs and communicates with the Near Field Communication (NFC) to identify the sticker and receive a unique identification (UTD). The cell phone application, loaded with the payment token or single-use virtual payment card, communicates with the server, transferring the token and UID and requesting refueling.

[0068] The server checks the policy (for example, whether refueling is allowed at a certain time) and balance associated with the UID and approves or rejects the refueling request. If the policy and balance are correct and there is a connection to the faucet, the server returns a confirmation to refuel to the application on the cell phone.

[0069] The identification between the Europay, Mastercard, Visa (EMV), the credit company, and the server is done through the application. The user is instructed to link their cell phone to the EMV. The cell phone communicates with the EMV at the gas station via NFC and transfers a token. The EMV requests transaction approval from the credit company, which contacts the server with the token number and refueling transaction details. The server identifies the transaction and approves a payment frame or payment request, provided there is a proper connection between the pump gun and the refueling nozzle.

[0070] Upon completion of the refueling, the refueling details may be transferred to the payment server of the credit cards company. The payment for refueling is made, and the server is charged and reported for the transaction. This innovative system, device, and method of digital payment for vehicle usage thus streamlines the refueling process, enhancing convenience, security, and efficiency.

[0071] In some other demonstrative embodiments, a refueling application operating on a mobile communication device may control a refueling system. For example, the refueling application may be configured to: instruct a user to insert a refueling gun into a fuel tank inlet of a vehicle (Step A) and monitor a link between the refueling gun and the refueling inlet, wherein the monitoring is done by receiving a signal from a sensor that detects that the refueling gun is inserted into the fuel tank inlet (Step B), reports to the server the status of the link, thus the vehicle may be ready for refuelingas long as there is a link between the refueling gun and the fuel tank inlet. For example, if the link has been disconnected, the server may order the payment server, e.g., the credit card company, to stop the transaction and the refueling.

[0072] Furthermore, the refueling application may be configured to identify the customer and the server (Step C) by instructing the user to attach the communication mobile device, e.g., the cell phone, to the identification device, e.g., a sticker, installed, e.g., affixed, to the vehicle, using near field communication (NFC) to receive a unique identification (UID), providing the server the payment token with no balance and the UID and requesting the server to enable refueling based on the user balance at the server and the UID, wherein, the server may check: a policy of payment, e.g., refueling the vehicle at a certain time, and a balance of the user account associated with the UID and approves or rejects the refueling request (at this stage the server still does not know which gas station it is) and if the request for refueling is according to the policy and the costumer balance is sufficient and the refueling gun is linked to the fuel tank inlet, the server may return to the refueling application a confirmation to refuel.

[0073] In this demonstrative embodiment, the refueling application may control the payment process (Step D). For example, the refueling application may instruct the user / customer to link the mobile communication device, e.g., cell phone, to the payment terminal, e.g., EMV terminal, at the gas station using NFC for transferring the payment token, e.g., credit card number, and the payment terminal, e.g., the terminal may apply for approval of the transaction to the payment server, e.g., the credit company card.

[0074] For example, the credit company may provide a payment request to the server with the token number and details of the refueling transaction and the server approves the payment request identifies the transaction, may identify the link between the pump gun and the refueling inlet, may approve a payment frame or the payment request based on the link, and may return to the payment terminal, e.g., EMV terminal, a confirmation to start refueling.

[0075] In this embodiment, the refueling application may instruct the user / customer to start refueling and monitor the link between the refueling gun and the fuel tank inlet. When the refueling ends, the refueling application transfers the refueling data to thepayment server, e.g., the credit card company, and may receive a paper receipt for the payment from the payment terminal and / or a digital receipt from the payment server and / or the server (Step E).

[0076] In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of some embodiments. However, it will be understood by persons of ordinary skill in the art that some embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, units, and / or circuits have not been described in detail so as not to obscure the discussion.

[0077] Discussions made herein utilizing terms such as, for example, "processing," "computing," "calculating," "determining," "establishing," "analyzing," "checking," or the like, may refer to operation(s) and / or process(es) of a computer, a computing platform, a computing system, or other electronic computing devices, that manipulate and / or transform data represented as physical (e.g., electronic) quantities within the computer's registers and / or memories into other data similarly represented as physical quantities within the computer's registers and / or memories or other information storage medium that may store instructions to perform operations and / or processes.

[0078] The terms "plurality" and "a plurality," as used herein, include, for example, "multiple" or "two or more." For example, "a plurality of items" includes two or more items.

[0079] References to "one embodiment," "an embodiment," "demonstrative embodiment," "various embodiments," etc., indicate that the embodiment(s) so described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Further, repeated use of the phrase "in one embodiment" does not necessarily refer to the same embodiment, although it may.

[0080] As used herein, unless otherwise specified, the use of the ordinal adjectives "first," "second," "third," etc., to describe a common object merely indicate that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or any other manner.

[0081] As used herein, the term "circuitry" may refer to, be part of, or include, an Application Specific Integrated Circuit (ASIC), an integrated circuit, an electronic circuit, a processor (shared, dedicated, or group), and / or memory (shared, dedicated, or group), that execute one or more software or firmware programs, a combinational logic circuit, and / or other suitable hardware components that provide the described functionality. In some demonstrative embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by one or more software or firmware modules. In some demonstrative embodiments, the circuitry may include logic, at least partially operable in hardware.

[0082] The term "logic" may refer, for example, to computing logic embedded in the circuitry of a computing apparatus and / or computing logic stored in a memory of a computing apparatus. For example, the logic may be accessible by a processor of the computing apparatus to execute the computing logic to perform computing functions and / or operations. In one example, logic may be embedded in various types of memory and / or firmware, e.g., silicon blocks of various chips and / or processors. Logic may be included in and / or implemented as part of various circuitry, e.g., radio circuitry, receiver circuitry, control circuitry, transmitter circuitry, transceiver circuitry, processor circuitry, and / or the like. In one example, logic may be embedded in volatile memory and / or non-volatile memory, including random access memory, read-only memory, programmable memory, magnetic memory, flash memory, persistent memory, and the like. Logic may be executed by one or more processors using memory, e.g., registers, stuck, buffers, and / or the like, coupled to one or more processors, e.g., as necessary to execute the logic.

[0083] The term "EMV," as used hereinbelow, is a payment method based upon a technical standard for smart payment cards and for payment terminals , and automated teller machines. EMV originally stood for "Europay, Mastercard, and Visa," the three companies which created the global payment standard.

[0084] The term "EMV terminal," as used hereinbelow, is a payment terminal also known as a Point of Sale (POS) terminal, credit card terminal, etc. The EMV terminal is a device that interfaces with payment cards, e.g., Europay, Mastercard, Visa, to make electronic funds transfers. The terminal typically consists of a secure keypad for entering a PIN, a screen, a means of capturing information from payments cards, anda network connection to access the payment network for authorization.

[0085] In some demonstrative embodiments, the payment terminal may allow a merchant to capture required credit and / or debit card information and transmit this data to the merchant services provider and / or bank for authorization and transfer funds to the merchant. The terminal may allow the merchant and / or their client to swipe, insert and / or hold a card near the device to capture the information.

[0086] The term "Card / s" as used hereinbelow, may include, for example, the prepaid card created and issued by an issuer, credit cards, debit cards, limited payment card or the like, and their digital representation in a payment application on a mobile device.

[0087] The term "mobile application" and / or "application" and / or "App" as used hereinbelow, may include at least one application which is installed on a computing device, e.g., a mobile device, for example, the loyalty club application, e-Wallet application, or the like. The mobile application may include the digital wallet SDK and may interact with a payment server. The mobile application may be configured to run on a mobile device operating system, such as, for example, iOS and Android and / or react and / or any other operating system.

[0088] The term "Payment token," as used hereinbelow, may include a unique placeholder called a payment token which is configured to include encrypted information of a payment ability of the user, for example, a credit card, a debit card, a prepaid card, a reloadable prepaid card, bank money transfer information, or the like. In some demonstrative embodiment, the payment token may be configured to access, retrieve, and maintain, for example, a customer's credit card information to ensure a higher level of security for both the customer and the business. The payment token may be saved on the customer platform and / or on the customer's mobile application.

[0089] The term "Radio Frequency Identification (RFID)" as used hereinbelow, may use electromagnetic fields to automatically identify and track tags attached to objects.

[0090] For example, an RFID system may include a tiny radio transponder, a radio receiver, and a transmitter. When triggered by an electromagnetic interrogation pulse from a nearby RFID reader device, the tag transmits digital data, usually an identifyinginventory number, back to the reader. This number can be used, for example, to track inventory goods, and / or provide a vehicle ID, if desired.

[0091] Passive RFID tags are powered by energy from the RFID reader's interrogating radio waves. Active RFID tags are powered by a battery and thus can be read at a greater range from the RFID reader up to hundreds of meters.

[0092] RFID tags are used in many industries. For example, an RFID tag attached to an automobile during production can be used to track its progress through the assembly line.

[0093] The disclosure, as described herein below, discloses a payment system that may be used at service stations for any type of vehicle for purchasing fuel or charging electric vehicles.

[0094] For example, the disclosure may provide a secure and efficient way to facilitate digital payments for fueling or charging a vehicle at a service station. The system may include a mobile device to read a vehicle identification from a communication device attached to the vehicle. The system then may send the vehicle identification to a payment server for issuing a payment token or a single-use virtual payment card based on the vehicle identification and a registered user credit allowance. The system may enable continuous monitoring of the refueling process and termination of the fueling when the refueling nozzle is detached from the vehicle.

[0095] Some embodiments may relate to the use of different technologies such as, for example, Near-Field Communication (NFC), Bluetooth, and Radio Frequency Identification (RFID) in facilitating secure digital payments for vehicle usage.

[0096] In some demonstrative embodiments, the system may include a mobile device configured to read a vehicle identification (VID) from a communication device attached to a vehicle, send the VID to a payment server for issuing a payment token, transfer the VID and the payment token to a payment terminal to enable fueling or charging of the vehicle, continuously monitor the presence of the refueling or charging nozzle in the vehicle's fuel tank or charging port, and receive a receipt for the payment made.

[0097] In some demonstrative embodiments, the system may also include a management server configured to control the fueling or charging process based on thestatus of the nozzle and approve or deny payment based on data received from the payment server.

[0098] In some demonstrative embodiments of the disclosure, a payment terminal may be configured to perform payments. For example, the payment terminal comprises processing circuitry, wherein the processing circuitry may be configured to: receive from a payment application installed on a mobile device vehicle data and a user identification (UID) via a near field communication (NFC), wherein the vehicle data comprise vehicle identification (ID) data transferred to the payment application from an information tag, e.g., RFID tag, installed on a vehicle. The payment terminal may send to a payment server the UID and the vehicle ID data within an authentication request message and receive from the payment server an authentication message, wherein the authentication is done based on the UID and the vehicle ID data and includes one or more usage rules.

[0099] For example, the payment terminal may send to the payment server a payment request message, and receive a payment from the payment server, wherein the payment may be triggered by a payment application of the mobile device.

[0100] Reference is now made to Figure 1, which illustrates a block diagram of a system 100 for performing payments for receiving services, e.g., fueling and / or charging at a service station according to some other demonstrative embodiments.

[0101] In some demonstrative embodiments, system 100 may include, for example, a vehicle 105 with a communication device 103, attached to the vehicle 105 in the vicinity of its fuel tank inlet 118, an application 125 installed on a mobile device 101, a management server 106, a payment server 111, and a service station 130. For example, the service station 130 may include a payment terminal 108, a fuel pump 114, and a fuel pump controller 135.

[0102] The communication device 103 may include a wireless communication component for transferring data from the communication device 103 to the application 125 on the mobile device 101. The wireless communication component may use RFID, Bluetooth, or any other known near field communication (NFC) technology. The communication device may be passive or active, powered by a dedicated battery or the battery of the vehicle 105.

[0103] The communication device 103 may also include a sensor or plurality of sensors, for detecting the presence of a refueling gun 116 in the fuel tank inlet 118. Detection of insertion 117 of refueling gun 116 into the fuel tank inlet 118 may be communicated via the communication device 103 to the mobile device 101. The sensor or sensors may also detect fuel flow into the fuel tank inlet 118, temperature, pressure, rate and other aspects of the refueling process. A unique identification (UID) of the vehicle 105 may also be stored on the communication device 103. The communication device 103 may also include a processor and a memory formore advanced capabilities, such as calculating refueling duration and storing past refueling data.

[0104] The mobile device 101 may comprise a near field communication (NFC) component for near field communication 102 with the communication device 103 and near field communication 107 with a payment terminal 108 at a service station 130. The mobile device 101 may be also in wireless communication 104 with a management server 106 via cellular network or Wi-Fi connectivity.

[0105] When a user arrives at a service station to refuel the vehicle 105, they may use the application 125 on the mobile device 101 to perform the refueling transaction. At the first stage, the application 125 may instruct the user to insert the refueling gun 116 of a fuel pump 114 into the fuel tank inlet 118 of the vehicle 105 and place the mobile device 101 within a wireless communication range of an identification device 103.

[0106] The communication device 103 may then transmit the unique identification (UID) of the vehicle 105 and a confirmation of presence the refueling gun 116 in the fuel tank inlet 118 to the application 125 via the near field communication (NFC) component in the mobile device 101.

[0107] In the next stage, the application 125 may report to the management server 106 that the refueling gun 116 is in the fuel tank inlet 118 associated with the UID. The UID stored in the identification device 103 may also be stored in the application 125 and / or management server 106 and limit the use of the application 125 only for refueling of vehicles with UID stored in the application 125.

[0108] The management server 106 may send a unique identifier of a single-use virtual payment card or other payment token 120 for use in a refueling transaction atthe service station 130 according to a refueling policy set in the management server 106 for the UID of the vehicle 105.

[0109] In the next stage, the user may use the application 125 to request 107, via the NFC component in the mobile device in communication with a payment terminal 108 at the service station, approval of the refueling transaction. The payment terminal 108 may request authorization 110 from a payment server 111 of a payment service provider such as a credit card issuer. The payment server 111 may then validate 112 the information of the single-use virtual payment card 120 with the management server 106.

[0110] Upon successful validation 112 of the information of the single-use virtual payment card 120 and any other terms concerning use of the single-use virtual payment card 120 set in the payment server 106, such as available funds in the user account, credit limit, transaction location, transaction type or transaction amount, the management server may authorize 112 payment server 111 to approve the refueling transaction.

[0111] The payment server 111 then send an approval of the refueling transaction to the payment terminal 108 and / or fuel pump controller 135, which in turn, instructs the fuel pump 114 to open, allowing the user to refuel the vehicle 105 with refueling gun 116 attached to the fuel pump 114.

[0112] In some demonstrative embodiments, the communication device 103 may report to the application 125 in real-time when the refueling gun 116 is removed from the fuel tank inlet 116. The application 125 may then send an instruction to the management server 106 or payment terminal 108 to stop the refueling transaction.

[0113] In some demonstrative embodiments, when the fueling of vehicle 105 ends, mobile device 105 may receive a receipt (line 107) from the payment terminal 108 on the amount of payment based on the amount of fuel fueled into vehicle 105. For example, the receipt may include the amount of fuel, the vehicle details, and the total sum for payment.

[0114] In some demonstrative embodiments, the management server 106 may include a fleet manager server configured to manage a vehicle fleet of one or more companies. The fleet manager server may include VIDs, driver ID, statistics on thevehicle usage, and any other related information.

[0115] In some demonstrative embodiments, the management server 106 may be configured to issue the payment card 120, for example, EMV card. The payment card 120 may include a predefined amount of money for paying for the service based on historical usage data of vehicle 105.

[0116] In some demonstrative embodiments, the management server 106 may continuously receive a status of the presence of the fuel pump 116 (link 117) in the fuel tank inlet 118. The management server 106 may be configured to instruct a fuel pump controller 135 at the service station 130 to initiate the fueling of a selected fuel pump, e.g., fuel pump 114, based on the status and may instruct the fuel pump controller 135 at the service station 103 to terminate the fueling of the selected fuel pump, e.g., fuel pump 114, based on the status.

[0117] In some demonstrative embodiments, the management server 106 may be configured to approve or deny payment based on data received from a payment server 111.

[0118] In some demonstrative embodiments, the payment server 111 may be operably coupled to the management server 106 (line 112). For example, the payment server 111 may be configured to issue the payment card 120 and may load the payment card 120 with a predefined amount of money for paying for the service based on historical usage data of vehicle 105 received from the management server 106. The payment server may be further configured to perform the payment for the fueling using the issued payment card 120.

[0119] In some demonstrative embodiments, the process of fueling vehicle 105 may start by entering the refueling gun 116 into the fuel tank inlet 118. The mobile device 101 may read (line 102) the VID and the fueling nozzle 116 status from a communication device 103 using near-field communication (NFC), Bluetooth technology, and / or any other suitable radio communication technology. For example, mobile device 101 may transfer the VID and the refueling gun 116 status to the management server 106.

[0120] In some demonstrative embodiments, the process of fueling may proceed with the mobile device 105 and may transfer via radio communication the paymentcard details, e.g., the VID, the driver details and / or any other requested details, to payment terminal 108. For example, the payment terminal 108 may authenticate the data with the management server 106 and / or payment server 111, and if authenticated, the payment terminal 108 may instruct the fuel pump controller 135 to activate the fuel pump 114 for fueling.

[0121] In some demonstrative embodiments, the communication device 103 may include a movement sensor (not shown) configured to detect an insertion of the refueling gun 116 to the fuel tank inlet 118 and a radio to continuously report on a refueling nozzle movement, e.g., status, while refueling the vehicle 105.

[0122] In some demonstrative embodiments, the communication device 103 may include a radio frequency identification (RFID) tag.

[0123] In some demonstrative embodiments, during the fueling process, mobile device 101 may be configured to continuously monitor communication device 103 using, for example, Bluetooth technology for the status of the refueling gun 116.

[0124] In some demonstrative embodiments, the communication device 103 may include an application 125. For example, the application 125 may be configured to: provide step-by-step guidance to a user on how to perform a fueling process as described above, e.g., insert the refueling gun 116 into the fuel tank inlet 118, touch the communication device 103, touch the payment terminal 108, start fueling and hold the mobile device 101 during all the process of fueling. At the end of the fueling the payment terminal 108 may use the issued payment car to charge for fueling the vehicle.

[0125] In some demonstrative embodiments, the communication device 103 may be configured to transfer data to application 125. For. example, the data may include at least one of vehicle type, a vehicle number, a vehicle owner, and a fuel type.

[0126] In some demonstrative embodiments, when vehicle 105, for example, may be authenticated and authorized by the management server 106 and / or the payment server 111 based on the UID and the VID data, the management server 106 and / or the payment server 11 Imay be configured to approve the payment based on one or more usage rules and to transfer a payment to the payment terminal 108 (line 109).

[0127] For example, after approval of the payment, the payment terminal 108 maycause an activation of, for example, the fueling pump 114 for fueling (line 113).

[0128] In another example, after the approval of the payment, the payment terminal 108 may cause the activation of a charging station (not shown) for charging an electric vehicle.

[0129] In some demonstrative embodiments, the approval of the payment may be done according to one or more usage of rules. For example, the one or more usage rules may include at least one of: a rule for verifying a time has passed since a time of a last fueling event; a rule for verifying an amount of fuel based on an average amount of fuel; a rule for verifying a vehicle identity based on a camera image; a rule for verifying a place of fueling based on historical records of fueling; a rule for setting a limitation on spending; a rule for setting a limitation on a merchant based on the merchant identification (MID); a rule for setting a limitation on a merchant type; a rule for setting a limitation on the minimum payment; a rule for setting a limitation on days, periods, or dates; a rule for setting a limitation on a region, and a rule for setting a limitation on a number of fueling events within a given period.

[0130] In some other demonstrative embodiments, the payment terminal 108 may transfer the VID data and UID to the management server 106 (line 109) and / or the payment server 111 (line 110).

[0131] For example, the management server 106 and / or the payment server 111 may be configured to receive data from the payment application 125, wherein the data may include at least one of the data configured to detect fraud, data of a current fueling, and vehicle data.

[0132] In some demonstrative embodiments, when, for example, vehicle 105 may be equipped with a fueling payment system, the payment application 125 may receive the VID data from, for example, the RFID tag attached to a vehicle fuel tank inlet. The RFID tag may transmit the VID data when the nozzle 116 of the fuel pump 114 may touch the vehicle fuel tank fill inlet 118.

[0133] In some other demonstrative embodiments, when, for example, vehicle 105 is an electric vehicle and equipped with a fueling payment system (not shown), the payment application 125 may receive the VID data from the RFID tag attached to a vehicle electrical charging outlet when a plug of a battery charger touches the vehicleelectrical charging outlet.

[0134] For example, when vehicle 105 may be equipped with a fueling payment system, when a fuel pump nozzle touches 118, the vehicle fuel tank fill inlet 118, the information tag 103 starts to transfer data to the payment application 125, and the management server 106 and / or the payment server 111 may be configured to receive the data from the payment application 125, wherein the data comprise at least one of a vehicle type, a vehicle number, a vehicle owner, and a fuel type.

[0135] When the fueling is ended, the communication device 103 (e.g., RFID) may be configured to transfer an end-of-fueling message and a sum of payment to the payment application 125. For example, the end-of-fueling message may include the fueling data.

[0136] In some other demonstrative embodiments, the management server 106 and / or the payment server 11 Imay receive from the vehicle fleet management server (not shown) a set of rules defining the terms of use for each vehicle of the fleet and may report back to the fleet management server on an attempt of fraud, fueling data and other usage data, if desired.

[0137] In some other demonstrative embodiments, the method for receiving the payment by system 100 may include stages, as described by the examples below. However, it should be understood that the embodiments of the present disclosure are not limited to the stages described below. Some embodiments may include fewer stages, and some other embodiments may include more stages.

[0138] For example, the first stage may include receiving data using application 125. For example, a portion of the data from vehicle 105 may be received via NFC and / or RFID reader (RFID tag), and / or a camera of the mobile device 101 (a Quick Response (QR) sticker), and the like. The second stage may include receiving from the management server 106 and / or the payment server 111 another portion of the data, for example, by wireless communication and / or from one or more sensors and / or components of the mobile device 101, if desired.

[0139] For example, the data may include at least one of: a payment token 120, e.g., a single-use virtual payment card, received from the management server 106 and / or the payment server 111, a vehicle identification received by touching a tag attached to thevehicle, e.g., NFC, (line 102), the UID of a user that logged in to the application 125, a first timestamp of a receiving data transaction, and a location of the mobile device 125 at the time of receiving the data transaction.

[0140] For example, the third stage may include sending data by application 125 when touching the payment terminal 108. The data may include at least one of: the payment token or a single-use virtual payment card, the vehicle identification, and the user identification.

[0141] For example, the fourth stage may include sending data to the management server 106 and / or the payment server 111 by application 125 (line 104). The data may be transferred via a wireless medium, such as, for example, cellular communication, satellite communication, or the like. The data may include at least one of: the VID, the UID, the first timestamp and / or the location of the mobile device 101.

[0142] For example, the fifth stage may include sending data (line 109) to the management server 106 and / or the payment server 111 by the payment terminal 108. For example, the data may include at least one of: the payment card 120, e.g., the payment token or single-use virtual payment card, requested vehicle service data by the user, the VID, the UID, a location of the payment terminal 108, and a second timestamp of performing data transactions and / or the like.

[0143] For example, the sixth stage may include generating by the management server 106 and / or the payment server 111 transaction decision by cross-referencing the first timestamp, the location of the payment terminal 108, the location of the mobile device 101, and the second timestamp and / or by checking whether the transaction of the requested vehicle service data is in a condition to be approved.

[0144] For example, if the transaction decision is approved, the management server 106 and / or the payment server 111 may be configured to send an approval data message (line 109) to the payment terminal 108 to authorize payment for the vehicle service, else the management server 106 and / or the payment server 111 may be configured to decline the payment for the vehicle service.

[0145] Reference is now made to Figure 2, which illustrates a flow chart of a method 200 for performing payments for fueling and / or charging an authorized vehicle according to some other demonstrative embodiments.

[0146] In some demonstrative embodiments, method 200 may start with a mobile device, e.g., mobile device 105 (Figure 1), which reads a vehicle identification (VID) from a communication device, e.g., communication device 105 (Figure 1), attached to a vehicle in the vicinity of a fuel tank inlet, e.g., fuel tank 118 (Figure 1)), as is shown in text box 210. It should be understood that the vehicle may be a running-by-fuel vehicle and / or an electric vehicle, a plug-in vehicle, a hybrid vehicle, or the like. For example, reading the VID from the communication device may be done by using a near-field communication (NFC) radio.

[0147] In some demonstrative embodiments, mobile device 103 may send the VID to a payment server, e.g., payment server 111 (Figure 1) via a management server, e.g., the management server 106 (Figure 1), for issuing a payment token or single-use virtual payment card, based on the VID and a registered user allowance credit (text box 220). For example, the payment token may include a predefined amount of money for paying for the service based on a payment request received from the service station.

[0148] In some demonstrative embodiments, mobile device 103 may transfer the VID and the issued payment token to a payment terminal, e.g., payment terminal 108 (Figure 1), to enable fueling the vehicle, e.g., vehicle 105 (Figure 1), by a fueling pump, e.g., fueling pump 114 (Figure 1), that serves the vehicle after a refueling nozzle, e.g., refueling gun 116 (Figure 1), is inserted into the fuel tank inlet, e.g., fuel tank inlet 118 (Figure 1) of the vehicle 105 (text box 230).

[0149] In some demonstrative embodiments, mobile device 103, may continuously receive from, for example, the communication device 103, an indication of the presence of, for example, the refueling gun 116 in the fuel tank inlet 118 (text box 240) and may continuously report the presence of, for example, the refueling gun 116 in the fuel tank inlet 118 to the management server 106.

[0150] In some demonstrative embodiments, an application, e.g., application 125 (Figure 1), installed on the mobile device and may receive data from the communication device. For example, the data may include at least one of vehicle type, a vehicle number, a vehicle owner, a fuel type, and any other data.

[0151] For example, the management server 106 may be configured to terminate the fueling when communication device 103 reports that the refueling nozzle 116 isdetached from vehicle 105 (text box 250). For example, the communication device may use Bluetooth technology to communicate with the mobile device. For example, the communication device may include an RFID tag.

[0152] In some demonstrative embodiments, mobile device 103 may receive a receipt from the payment terminal 108 on the amount of payment done using the payment token or single-use virtual payment card. For example, the payment amount may be based on the fuel fueled into the vehicle (text box 260).

[0153] In some demonstrative embodiments, an application, e.g., application 125 (Figure 1), may be installed on the mobile device, and the installed application may provide a step-by-step guidance on how to perform a fueling process of the vehicle. Furthermore, the application may be used to pay for fueling the vehicle with the issued payment token.

[0154] Reference is made to Figure 3, which illustrates a block diagram of a system 100 for performing payments for maintenance and / or usage of an authorized vehicle, according to some demonstrative embodiments.

[0155] In some demonstrative embodiments, system 300 may include a payment server 310, a computing device 320, a payment terminal 330, and a vehicle identification (ID) device 350. The vehicle ID device may include an active or passive RFID tag 350 attached to a vehicle 340.

[0156] In some demonstrative embodiments, the payment card and the vehicle may belong to a company. Thus, authorized use and / or supervision of the payment card may be required.

[0157] In some demonstrative embodiments, payment server 310 may include processing circuitry 311, a group tokens database 312, a payment module 314, a payment approval module 315, an authentication module 316, and a communication unit 317.

[0158] In some demonstrative embodiments, processing circuitry 311 may include circuits, logic, memory, an operating system, one or more cores of a computer, a graphic processor, a digital signal processor, or the like.

[0159] In some demonstrative embodiments, payment server 310 may include oneor more group token databases 312. The one or more group tokens database 312 may include and\or store one or more tokens of one or more business groups. For example, a group tokens database of the one or more group tokens databases 312 may include one or more payment tokens of one or more clients, respectively, e.g., a payment token 335. For example, the business group may include loyalty clubs, companies, organizations, and the like.

[0160] In some demonstrative embodiments, a digital payment token 335 may include user data arranged according to a Europay, Visa, Mastercard (EVM) standard. The digital payment token 335 may also be referred to as a digital EVM token.

[0161] In some demonstrative embodiments, the payment module 314 may be configured to transfer the requested amount of benefit to a merchant account, to update the business group account and the client account.

[0162] In some demonstrative embodiments, authentication module 316 may be configured to store one or more sets of rules. For example, the set of rules may include rules to verify that the vehicle 350 is authorized to be paid for the fuel.

[0163] For example, the set of rules may include usage rules. The usage rules may include at least one rule from the following list:

[0164] a rule for verifying that time has passed since the time of the last fueling event;

[0165] a rule for verifying an amount of fuel based on an average amount of fuel;

[0166] a rule for verifying a vehicle identity based on a camera image;

[0167] a rule for verifying a place of fueling based on historical records of fueling;

[0168] a rule for setting a limitation on spending, for example, the user can spend only a predetermined amount of money, e.g., $100.

[0169] a rule for setting a limitation on a merchant based on the merchant identification (MID), for example, the purchasing can take place only with MID = 1234.

[0170] a rule for setting a limitation on a merchant type, for example, the user may buy only fuel, e.g., Merchant category code (MMC):::fuel.

[0171] a rule for setting a limitation on a minimum pay;

[0172] a rule for setting a limitation on days, periods, or dates;

[0173] a rule for setting a limitation on a region; and

[0174] a rule for setting a limitation on a number of fueling events within a given period.

[0175] In some demonstrative embodiments, payment approval module 315 may be configured to receive a payment approval request from, for example, the payment terminal 330. The payment approval module 315 may process the request based on one or more sets of rules and the account balance of the payment token holder. The payment approval module 315 may send an approval or denial to payment terminal 330 based on the processing.

[0176] Although, it should be understood that in some other embodiments, each of the payment module 314, the payment approval module 315, and the authentication module 316 may be implemented by software and / or hardware and / or by a combination of software and hardware.

[0177] In some demonstrative embodiments, processing circuity 311 is configured to send approval or denial response to the payment request based on the processing through the communication unit 317.

[0178] In some demonstrative embodiments, processing circuitry 311 may be configured to receive an approval request message from payment terminal 330.

[0179] In some demonstrative embodiments, the computing device 320, e.g., mobile device, may include an application 324. For example, the application may include a software development kit (SDK) 326 with the digital payment token, e.g., token 335, and a communication unit 322.

[0180] In some demonstrative embodiments, the computing device may be a cell phone, a tablet, a digital wallet device, a smartwatch, a laptop computer, and / or any type of computerized personal and / or mobile device.

[0181] In some demonstrative embodiments, SDK 326 may be embedded in the digital wallet application 324.

[0182] In some demonstrative embodiments, communication unit 322 may include, for example, a Near Field Communication (NFC) radio which may enable a secure transaction of the digital payment token 335 to the payment terminal 330, and an information tag reader (not shown), e.g., RFID reader.

[0183] It should be understood that communication unit 322 may include one or more different types of radios. For example, a cellphone radio, WiFi radio, 60 GHz radio, RFID, Bluetooth, an RFID reader, and the like.

[0184] In some demonstrative embodiments, a payment terminal 330 may be configured to execute payments. The payment terminal 330 may include a communication unit 332, a token reader and / or payment card reader 334, processing circuitry 336, and an interaction unit 338.

[0185] in some other embodiments, for example, payment terminal 330 may be referred to as EMV terminal.

[0186] In some demonstrative embodiments, communication unit 332 may include, for example, a Near Field Communication (NFC) radio which may enable a secure transaction of the digital payment token 335 to the payment terminal 320.

[0187] In some demonstrative embodiments, the processing circuitry 336 may be configured to receive from a payment application 324 installed on a mobile device 320 vehicle ID data and / or a user identification (UTD) via an NFC. For example, vehicle ID data and / or the UTD may be transferred to the payment application 324 from, for example, an RFID tag 350 attached to vehicle 340.

[0188] In some demonstrative embodiments, the RFID tag 350 may include a passive RFID tag or an active RFID tag.

[0189] In some demonstrative embodiments, the payment application 324 may be configured to receive the payment data from the RFID tag 350 via wireless communication.

[0190] In some demonstrative embodiments, the payment application 324 may be configured to receive the vehicle ID data 355 from the RFID tag 350. For example, the RFID tag 350 may be attached to a vehicle fuel tank fill inlet (not shown), and when a nozzle of a fuel pump touches the vehicle fuel tank fill inlet, the RFID tag 350 maytransmit the vehicle ID data and / or the UID to the payment application 324.

[0191] In some demonstrative embodiments, the payment application 324 may be configured to receive the vehicle ID data from the RFID tag 350. For example, the RFID tag 350 may be attached to a vehicle's electrical charging outlet (not shown), and when a plug of a battery charger touches the vehicle's electrical charging outlet, the RFID tag 350 may transmit the vehicle ID data 355 and / or the UID to the payment application 324.

[0192] In some demonstrative embodiments, the payment terminal 330 may send a payment request message to the payment server 310, for example, the payment request message 360. For example, the payment request message 360 may include the requested payment for the fueling.

[0193] In some demonstrative embodiments, payment server 310 may include one or more payment card data and / or one or more tokens of a user, and the payment received based on the one or more payment card data.

[0194] In some demonstrative embodiments, payment server 310 may be to authenticate a request to purchase fuel with the payment application.

[0195] For example, the authentication model 316 may authenticate the request. The authentication may include at least one of verification on the time passed since the time of last fueling, verification on the amount of fuel based on an average amount of fuel, verification of a vehicle identity based on a camera image, and verification on a place of fueling based on historical records of fueling and any other limitations.

[0196] In some demonstrative embodiments, the payment application 324 may be configured to send an approval request message to the payment server 310 and receive an approval message from the payment server 310. For example, the approval message may include at least one of a fuel type, a fuel amount, a vehicle license number, and the amount of money to pay.

[0197] Advantageously, using a two stages method for paying for maintenance, e.g., fueling and / or charging, a vehicle, wherein the first stage may include authorizing a vehicle and the user to use a provided payment means to pay for the fueling and / or the charging, and the second stage may include making a payment with the payment token,e.g., a single-use virtual payment card and / or a standard payment card installed in a digital wallet to ensure misuse of the payment means. Thus, increasing the security of the purchasing using the digital wallet application.

[0198] Reference is now made to Figure 4, which is a schematic illustration of a flow chart of a method 400 for performing payment for vehicle maintenance by a payment application 324 (Figure 3), according to some demonstrative embodiments.

[0199] In some demonstrative embodiments, method 400 may start with receiving from an RFID tag attached to a vehicle a UTD (text box 410). For example, the UTD may include vehicle ID data and may be transferred to the payment application 324 (Figure 3) from a device attached to a vehicle, e.g., an RFID tag.

[0200] In some demonstrative embodiments, the payment application 324 (Figure 3) may transmit, using an NFC technology, a payment token and the UTD to a payment terminal to be transferred to the payment server by the payment terminal (text box 420).

[0201] In some demonstrative embodiments, vehicle 340 (Figure 3) may be authenticated and authorized by the payment server 310 (Figure 3) (diamond 430). If the user is authenticated, the payment terminal 324 may send an approval request message to the payment server and if the approval is received, the payment from the payment server (text box 450).

[0202] For example, the authentication may include verification of time passed since the time of the last fueling, verification on the amount of fuel based on an average amount of fuel, verification of a vehicle identity based on a camera image and\or verification of a location of fueling based on historical records of fueling and any other usage rules.

[0203] For example, the payment server 310 (figure 3) may include one or more payment tokens of a user, and the payment received may be based on one or more payment tokens. For example, a business company may issue one or more payment tokens, payment cards or single-use virtual payment cards, for their employees to pay the company's vehicle expenses.

[0204] In some demonstrative embodiments, if the authentication of the vehicle fails, the vehicle is unauthorized, and the payment process may be aborted (text box440).

[0205] In some demonstrative embodiments, the payment application 324 may receive a payment confirmation message for the payment server 310 (Figure 3) (text box 460).

[0206] In some other embodiments, the payment application may receive the vehicle ID data and / or UID from the RFID tag attached to a vehicle fuel tank fill inlet when a fuel pump nozzle touches the vehicle fuel tank fill inlet.

[0207] Yet, in some other embodiments, the payment application may receive the vehicle ID data and / or the UID from the RFID tag attached to a vehicle electrical charging outlet when a battery charger plug touches the vehicle electrical charging outlet.

[0208] Reference is now made to Figure 5, which illustrates a block diagram of a system 500 for performing payments for a maintenance of an authorized vehicle according to some other demonstrative embodiments.

[0209] In some demonstrative embodiments, system 500 may include a company server 510. For example, the company server may be a loyalty club server, or organization server, or any other commercial entity or company server. For example, the company server 510 may include users database 515. The users database 515 may include user data for each user, for example, the user data may include the payment card data of the user and / or a token data of the user, the company car license number, the company car type, the company card manufacturer name, the company car color and / or a set of usage rules and / or limitations for using the company card for fueling.

[0210] In some demonstrative embodiments, the set of usage rules and / or limitations may include, for example, a verification rule on time passed since the time of the last fueling, a verification rule on the amount of fuel based on an average amount of fuel, a verification rule of a vehicle identity based on a camera image, a verification rule on a place of fueling based on historical records of fueling, a rule for setting a limitation on spending, for example, the user can spend only a predetermined amount of money, e.g., $100, a rule for setting a limitation on a merchant based on the merchant identification (MID), for example, the purchasing can take place only with MID = 1234, a rule for setting a limitation on a merchant type, for example, the user may buyonly fuel, e.g., Merchant category code (MMC) = fuel, a rule for setting a limitation on a minimum pay, a rule for setting a limitation on days, periods, or dates, a rule for setting a limitation on a region, a rule for setting a limitation on a number of fueling events within a given period and / or any other rules or limitations

[0211] In some demonstrative embodiments, system 500 may include a payment server 520. For example, the payment server 520 may be used to issue payment cards and / or payment tokens for users, e.g., employees of one / or more companies and / or loyalty clubs and / or any other commercial entity users and / or employees.

[0212] In some demonstrative embodiments, payment server 520 may include the user token database 525 and / or the user database 515.

[0213] In some demonstrative embodiments, system 500 may include a mobile device 540, e.g., a computing device. For example, mobile device 540 may be the mobile device 320 (Figure 3).

[0214] In some demonstrative embodiments, mobile device 540 may include an SDK 545 and RFID reader 546. For example, SDK 545 may include a digital wallet. The digital wallet may store, for example, the company payment card and / or the company payment token, and / or any other payment cards / tokens.

[0215] In some demonstrative embodiments, system 500 may include a payment terminal 550 for receiving payment for fueling a vehicle and / or charging a battery of a vehicle.

[0216] In some demonstrative embodiments, the payment terminal 550 may be embedded and / or installed on a fuel pump 560 and / or a battery charger (not shown).

[0217] In some demonstrative embodiments, a vehicle 530 may include an identification device or tag, e.g., RFID tag 534. For example, the RFID tag 534 may be attached to a vehicle body near a fuel tank inlet 536.

[0218] In some demonstrative embodiments, the fueling of a vehicle with system 500 may be done as follows. For example, fueling has two stages of verification. For example, the first stage may include a user reading the RFID tag 534 using the digital RFID reader 546 installed on a mobile device 540. The RFID tag 534 may provide vehicle data, e.g., license number, vehicle manufacture name, vehicle model name andetc. The RFID tag 534 may also provide the user identification (UID), as shown with arrow A. The digital wallet, e.g., SDK 545, may provide the vehicle data and UID to payment terminal 550, as shown with arrow B.

[0219] The second stage may include, for example, verification of vehicle 530 against the user payment means, e.g., payment token or single-use virtual payment card, based on the vehicle data and the UID. For example, the payment terminal 550 may transfer to the payment server 520 at least one of the UID, usage data, and vehicle data (arrow C). For example, the usage data may include an amount of fuel limitation that can be provided to the vehicle 530.

[0220] In response, the payment server 520 may send an approval request message to the company server 510. For example, the approval request message may include the usage data and UID (arrow D), and in return, the company server 510 may send an approval / deni al message to the payment server 520 (arrow H). For example, the approval / deni al message may include, for example, the approved fuel amount and the fuel type.

[0221] In other demonstrative embodiments, the payment server 520 may approve or deny the fueling request.

[0222] In some demonstrative embodiments, the payment server 520 may return an approval message to the payment terminal 550 (arrow E), and the fueling may start (arrow F). After the fueling of vehicle 530 ends, the fuel pump 560 may provide usage data to the payment terminal 550 (arrow F). The payment terminal 550 may receive the payment from the digital wallet (arrow I) or by a physical payment card, e.g., a credit card, and may send receipt data to the payment server 520.

[0223] Figure 6 illustrates a method 600 for performing payment at a service station with a payment application, according to some demonstrative embodiments.

[0224] In some other demonstrative embodiments, the method 600 for paying for services at a service station for a vehicle using an application of a mobile device is disclosed.

[0225] For example, method 600 may start with, during the application setup, uploading a payment token or single-use virtual payment card from a payment serverand entering a user identification (text box 610). Method 600 may proceed with uploading from an information tag attached to the vehicle, a vehicle identification via an information tag reader (text box 620). Method 600 may proceed with transmitting, using an NFC, the user identification, the vehicle identification, and the payment token data by placing it within wireless communication range of a payment terminal (text box 630). For example, the payment terminal may be configured to send a payment request to the payment server, including the user identification, the vehicle identification, and the payment token data.

[0226] In some other demonstrative embodiments, method 600 may proceed to enable the reception of the service by touching the payment terminal when receiving approval from the payment server (text box 640) and receiving a digital receipt (text box 650). For example, the digital receipt may include at least one of a sum of payment, a vehicle mileage, a content of the service, and the user identification upon an end-of- service event. The method 700 may end with transferring receipt data to a company server to collect vehicle and user usage statistics (text box 660).

[0227] Figure 7 illustrates a block diagram of a system 700 for authenticating payments for receiving services, e.g., fueling and / or charging at a service station, according to some demonstrative embodiments.

[0228] In some demonstrative embodiments, system 700 may include a rule server 706 configured to generate and apply rules of usage of a payment card and / or a payment token. For example, the payment card and / or the token may include a credit card, a debit card, one time use payment card, a company card, a loyalty club card, and the like.

[0229] In some demonstrative embodiments, system 700 may include a fleet management server 707. For example, the fleet management server 707 may collect, store and / or provide data on vehicles of the fleet. For example, the data may include a company name, a vehicle identification, e.g., license plate number, a user identification, e.g., driver data, total mileage and / or kilometrage of the vehicle, history of services, fueling amount, charging amount, time between charging or fueling and the like.

[0230] For example, the management server 701 may include a payment module710. The payment module 710 may be configured to perform payments for services at a service station 764, e.g., fueling and / or charging a vehicle 705, based on a set of rules that may be received from rule server 706. The payment module 710 may be configured to authenticate a payment request that may be received from a payment terminal 703 based on the user data, e.g., vehicle data that may be received from the fleet management server 707.

[0231] For example, when vehicle 705 may need to be fueled, a user may use an application to transfer token data, e.g., payment token or single-use virtual payment card, user data, e.g., user ID, and vehicle data, e.g., vehicle ID, to payment terminal 764. Payment terminal 764 may send an authentication request 702 to payment module 710, and payment module 710 may authenticate the requested service based on the vehicle data and user data provided by fleet management server 707 and the set of rules provided by rule server 706. For example, the payment module 710 may open the fuel pump 764 to service if the request is approved. Upon ending to fuel vehicle 705, the payment module 710 may provide a requested payment to payment terminal 703. The payment terminal 703 may provide the application with a payment receipt and transfer the payment data to the fleet management server 707.

[0232] For example, the payment data may include the user ID, the vehicle ID, the mileage of the vehicle, the payment token data, the amount of fuel, and the total sum for payment.

[0233] Reference is now made to Figure 8, which is a schematic illustration of a product of manufacture 800, according to some demonstrative embodiments. Product 800 may include one or more tangible computer-readable non-transitory storage media 810, which may include computer-executable instructions 830, implemented by processing device 830, operable to, when executed by at least one computer processor, enable the at least one processing circuitry 311 (Figure 3) to implement one or more program instructions for performing payments related to vehicle maintenance using a payment application, and / or to perform, trigger and / or implement one or more operations, communications and / or functionalities as described above with reference to Figures 1-7. The phrase "non-transitory machine-readable medium" is directed to include all computer-readable media, with the sole exception being a transitory propagating signal.

[0234] In some demonstrative embodiments, product 800 and / or machine-readable storage medium 810 may include one or more types of computer-readable storage media capable of storing data, including volatile memory, non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writeable or re-writeable memory, and the like. For example, machine-readable storage medium 410 may include any type of memory, such as, for example, RAM, DRAM, ROM, programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), Flash memory, a hard disk drive (HDD), a solid-state disk drive (SDD), fusion drive, and the like. The computer-readable storage media may include any suitable media involved with downloading or transferring a computer program from a remote computer to a requesting computer carried by data signals embodied in a carrier wave or other propagation medium through a communication link, e.g., a modem, radio, or network connection.

[0235] In some demonstrative embodiments, processing device 830 may include logic. The logic may include instructions, data, and / or code, which, if executed by a machine, may cause the machine to perform a method, process and / or operations as described herein. The machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, a computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware, software, firmware, and the like.

[0236] In some demonstrative embodiments, processing device 830 may include or may be implemented as software, firmware, a software module, an application, a program, a subroutine, instructions, an instruction set, computing code, words, values, symbols, and the like. Instructions 840 may include any suitable types of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Instructions may be implemented according to a predefined computer language, manner, or syntax, for instructing a processor to perform a specific function. The instructions may be implemented using any suitable high-level, low- level, object-oriented, visual, compiled, and / or interpreted programming languages, such as C, C++, C#, Java, Python, BASIC, Mat lab, assembly language, machine code, and the like.

[0237] It is to be understood that the system and / or the method for performingpayments using a payment application of a mobile device to pay for a service to a vehicle at a service station is described hereinabove by way of example only. Other embodiments may be implemented based on the detailed description and the claims that followed.

[0238] It is to be understood that numerals in the drawings represent elements through several figures and that not all components and / or steps described and illustrated with reference to the figures are required for all embodiments or arrangements.

[0239] It should also be understood that the embodiments, implementations, and / or arrangements of the systems and methods disclosed herein can be incorporated as a software algorithm, application, program, module, or code residing in hardware, firmware, and / or on a computer useable medium (including software modules and browser plug-ins) that can be executed in a processor of a computer system or a computing device to configure the processor and / or other elements to perform the functions and / or operations described herein.

[0240] It should be appreciated that according to at least one embodiment, one or more computer programs, modules, and / or applications that, when executed, perform methods of the present disclosure need not reside on a single computer or processor but can be distributed in a modular fashion amongst a number of different computers or processors to implement various aspects of the systems and methods disclosed herein.

[0241] Thus, illustrative embodiments and arrangements of the present systems and methods provide a computer-implemented method, computer system, and computer program product for processing code(s). The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments and arrangements. In this regard, each block in the flowchart or block diagrams can represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).

[0242] It should be noted that, in some alternative implementations, the functions noted in the block can occur out of order noted in the figures. For example, two blocksshown in succession may be executed substantially concurrently, or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved.

[0243] It will also be noted that each block of the block diagrams and / or flowchart illustration, and combinations of blocks in the block diagrams and / or flowchart illustration, can be implemented by particular purpose hardware-based systems that perform the specified functions or acts or combinations of specialized purpose hardware and computer instructions.

[0244] The terminology used herein is to describe particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0245] Also, the phraseology and terminology used herein are for the purpose of description and should not be regarded as limiting. The use of "including," "comprising," or "having," "containing," "involving," and variations thereof herein is meant to encompass the items listed thereafter and equivalents thereof as well as additional items.EXAMPLES

[0246] The following examples pertain to further embodiments.

[0247] Example 1 includes a payment terminal is configured to perform payments, the payment terminal comprises processing circuitry, wherein the processing circuitry is configured to: receive from a payment application installed on a mobile device a service request comprising vehicle data via a near field communication (NFC), wherein the vehicle data comprise vehicle identification (VID) data which is transferred to the payment application from an information tag attached to a vehicle;send to a payment server an authentication request message comprising a user identification (UID) and the VID data; receive from the payment server an authentication message, wherein the authentication is done based on the UID and the VID data; and receive a service usage limitation instruction from the payment server, wherein the service usage limitation instruction is based on one or more usage rules.

[0248] Example 2 includes the subject matter of Example 1, and optionally, the payment terminal is configured to: send to the payment server a payment request message, wherein the payment request message includes VID data; and receive a payment from the payment server, wherein the payment is triggered by a payment application of the mobile device.

[0249] Example 3 includes the subj ect matter of Example 1 , and optionally, wherein the information tag is attached to the vehicle, comprises a radio frequency identification (RFID) tag.

[0250] Example 4 includes the subj ect matter of Example 1 , and optionally, wherein the payment application is configured to receive the VID data from the RFID tag.

[0251] The payment terminal of claim 1, wherein the information tag comprises a QR sticker, and the payment application is configured to receive the VID data by reading the QR code.

[0252] Example 5 includes the subject matter of Example 3, and optionally, wherein when a fuel pump nozzle touches the vehicle fuel tank fill inlet, the payment application is configured to receive the VID data from the RFID tag attached to a fuel tank fill inlet.

[0253] Example 6 includes the subject matter of Example 3, and optionally, wherein when a plug of a battery charger touches the vehicle electrical charging outlet, the payment application is configured to receive the VID data from the RFID tag attached to a vehicle electrical charging outlet.

[0254] Example 7 includes the subject matter of Example 1, and optionally, wherein the payment server comprises one or more payment card data and the payment received from a user account of the one or more payment card data.

[0255] Example 8 includes the subject matter of Example 1, and optionally, whereinthe payment server is configured to approve a request to purchase a service using the one or more usage rules.

[0256] Example 9 includes the subj ect matter of Example 1 , and optionally, wherein the one or more usage rules comprise at least one of a rule for verifying a time has passed since a time of a last fueling event; a rule for verifying an amount of fuel based on an average amount of fuel; a rule for verifying a vehicle identity based on a camera image; a rule for verifying a place of fueling based on historical records of fueling; a rule for setting a limitation on spending; a rule for setting a limitation on a merchant based on the merchant identification (MID); a rule for setting a limitation on a merchant type; a rule for setting a limitation on a minimum pay; a rule for setting a limitation on days, periods, or dates; a rule for setting a limitation on a region; and a rule for setting a limitation on a number of fueling events within a given period.

[0257] Example 10 includes the subject matter of Example 1, and optionally, wherein the payment server is configured to receive first data from the payment application and a second data from the payment terminal, wherein the data comprise at least one of: data configured to detect fraud, data of a current fueling, and the vehicle data and the payment server is configured to: detect fraud by comparing the first data to the second data to detect a mismatch between the first data and the second data that indicate a possible attempt to perform fraud.

[0258] Example 11 includes the subject matter of Example 1, and optionally, when a fuel pump nozzle touches a vehicle fuel tank fill inlet, the information tag starts to transfer data to the payment application, and the payment server is configured to receive the data from the payment application, wherein the data comprise at least one of a vehicle type, a vehicle number, a vehicle owner, and a fuel type.

[0259] Example 12 includes the subject matter of Example 1, and optionally, when the fueling is ended, the information tag is configured to transfer an end-of-fueling message and a sum of payment to the payment application, wherein the end-of-fueling message comprises fueling data.

[0260] Example 13 includes a method for performing payments using a payment application of a mobile device, the method comprising: receiving from an information tag installed on a vehicle, vehicle data, comprise vehicle identification (VID) data viaan information tag reader, wherein the VID data are transferred to a payment application from the information tag attached to the vehicle; transmitting the VID data and a user identification (UID) via a near field communication (NFC) to a payment terminal to be transferred by the payment terminal to a payment server; and when the vehicle is authenticated and authorized by the payment server based on the UID and the VID data, the payment server is configured to approve the payment based on one or more usage rules and to transfer a payment to the payment terminal .

[0261] Example 14 includes the subject matter of Example 13, and optionally, wherein the information tag comprises an RFID tag, and the method comprises: receiving the VID data from the RFID tag.

[0262] Example 15 includes the subject matter of Example 14, and optionally, when a nozzle of a fuel pump touches the vehicle fuel tank fill inlet, receiving the VID data from the RFID tag attached to a vehicle fuel tank fill inlet.

[0263] Example 16 comprises: when a plug of a battery charger touches the vehicle electrical charging outlet, receiving the vehicle data from the RFID tag attached to a vehicle electrical charging outlet.

[0264] Example 17 includes the subject matter of Example 13, wherein the payment server comprises one or more tokens of a business entity having a plurality of users and the payment received from an account of the one or more payment tokens.

[0265] Example 18 includes the subject matter of Example 13, wherein the payment server comprises one or more payment cards of a business entity having a plurality of users and the payment received from an account of the one or more payment card data.

[0266] Example 19 includes the subject matter of Example 13, wherein the one or more usage rules comprise at least one of: a rule for verifying a time has passed since a time of a last fueling event; a rule for verifying an amount of fuel based on an average amount of fuel; a rule for verifying a vehicle identity based on a camera image; a rule for verifying a place of fueling based on historical records of fueling; a rule for setting a limitation on spending; a rule for setting a limitation on a merchant based on the merchant identification (MID);a rule for setting a limitation on a merchant type; a rule for setting a limitation on a minimum pay; a rule for setting a limitation on days,periods, or dates; a rule for setting a limitation on a region; and a rule for setting a limitation on a number of fueling events within a given period.

[0267] Example 20 includes the subject matter of Example 13, wherein the payment server is configured to receive first data from the payment application and a second data from the payment terminal, wherein the data comprise at least one of: data configured to detect fraud, data of a current fueling, and the vehicle data and the payment server is configured to: detect fraud by comparing the first data to the second data to detect a mismatch between the first data and the second data that indicate a possible attempt to perform fraud.

[0268] Example 21 includes the subject matter of Example 13, when a fuel pump nozzle touches a vehicle fuel tank fill inlet, the information tag starts to transfer data to the payment application and the payment server is configured to receive the data from the payment application, wherein the data comprise at least one of a vehicle type, a vehicle number, a vehicle owner, and a fuel type.

[0269] Example 22 includes the subject matter of Example 13, when the fueling is ended, the information tag is configured to transfer an end-of-fueling message and a sum of payment to the payment application, wherein the end-of-fueling message comprises fueling data.

[0270] The subject matter described above is provided by way of illustration only and should not be construed as limiting. Various modifications and changes can be made to the subject matter described herein without following the example embodiments and applications illustrated and described and without departing from the true spirit and scope of the present invention, which is set forth in the following claims.

Claims

CLAIMSWhat is claimed is:

1. A system for refueling a vehicle (105) at a service station performed by an application (125) installed in a mobile device (101), configured to: instruct a user to insert a refueling gun (116) of a fuel pump (114) into a fuel tank inlet (118) of a vehicle (105); instruct the user to place the mobile device within a wireless communication range of an identification device attached to the vehicle in the vicinity of the fuel tank inlet (118), wherein the identification device comprises a sensor which is configured to detect the presence of the refueling gun (116) in the fuel tank inlet (118); receive from the identification device a unique identification (UID) of the vehicle (105) and a confirmation of presence the refueling gun (116) in the fuel tank inlet (118) via a near field communication (NFC) component in the mobile device (101); report to the management server (106) that the refueling gun (116) is in the fuel tank inlet (118) associated with the UID; receive (104) from the management server (106) a unique identifier of a single-use virtual payment card (120) for use in a refueling transaction at the service station according to a refueling policy set in the management server for the UID; and request, via the NFC component in the mobile device in communication with a payment terminal (108) at the service station, approval of the refueling transaction.

2. The system of claim 1, wherein said sensor is configured to continuously monitor presence of the refueling gun (116) in the fuel tank inlet (118), and the mobile device is configured to receive a signal from the identification device (105) in real-time when the refueling gun (116) is removed from the fuel tank inlet (118) and report to the management server.

3. The system of claim 2, further configured to instruct the fuel pump (114) to stop refueling when the refueling gun (116) is removed from the fuel tank inlet (118).

4. The system of claim 2, wherein the management server is configured to calculate an overall refueling time between inserting and removing the refueling gun (116) from the fuel tank inlet (118) and assess whether the amount of the refueling transaction is consistent with the overall refueling time; and upon detecting that the overall refueling time is not consistent with the amount of the refueling transaction, flag the transaction as a potentially illegitimate transaction.

5. The system of claim 1, wherein the management server (106) is configured to load the single-use virtual payment card (120) with a limit corresponding to the amount required to be approved for initiating the refueling transaction.

6. The system of claim 1, wherein the application in the mobile device is configured to notify the user when the refueling gun (116) is inserted into or removed from the fuel tank inlet (118) associated with the UID stored in the application for the user.

7. The method of claim 1, wherein the mobile device is further configured to: instruct the user to place the mobile device (101) within a wireless communication range with a payment terminal (108) for initiating the refueling transaction; receive (110) through the payment terminal (108) an approval of the refueling transaction using the single-use virtual payment card (120).

8. The system of claim 7, wherein the approval is based on at least one of: a token usage policy, a user balance, a user payment card limit, a refueling location, a refueling hour, a fuel type.

9. The system of claim 1, wherein the communication device is configured to: transfer data to the application, wherein the data comprise at least one of: a vehicle type, a vehicle number, a vehicle owner, and a fuel type.

10. The system of claim 1, wherein the NFC component is a radio frequency identification (RFID) tag.

11. The system of claim 1, wherein the NFC component is a Bluetooth transmitter.

12. The system of claim 1, wherein the sensor is configured to detect the presence of the refueling gun by closing a circuit through a conducting part of the refueling gun.

13. The method of claim 1, wherein the management server is configured to load the single-use virtual payment card (120) with a limit corresponding to an amount of the refueling transaction received from the service station.

14. The method of claim 1, wherein the management server is configured to change a status of the single-use virtual payment card (120) to cancelled after completion of the refueling transaction.

15. The system of claim 1, wherein the sensor is configured to detect a specific characteristic of the refueling gun (116), such as its shape, size, or material composition, to distinguish it from other objects placed in the fuel tank inlet (118).

16. The system of claim 1, wherein the sensor comprises a magnetic field sensor configured to detect the magnetic signature of the refueling gun (116).

17. The system of claim 1, wherein the sensor comprises an optical sensor configured to detect the presence of the refueling gun (116) based on light reflection or interruption.

18. The system of claim 1, wherein the sensor is configured to monitor the fuel level in the fuel tank of the vehicle and the mobile device is configured receive a fuel level data from the sensor through the identification device, and to send an instruction to stop the refueling process when the fuel level is in or beyond a predetermined fuel limit.

19. The system of claim 1, wherein data from the sensor is integrated with date from the fuel pump (114) to provide real-time data on the refueling flow rate.

20. The system of claim 1, wherein the mobile device is securely paired with the identification device (105) using a unique identifier to prevent unauthorized communication.

21. The system of claim 1, further comprising a temperature sensor integrated with the sensor to monitor a temperature in the area of the fuel tank inlet during refueling and wherein the application on the mobile device is configured to generate an alert when the temperature is exceeding a predetermined temperature threshold.

22. The system of claim 1, further comprising a pressure sensor integrated with the sensor to monitor the pressure in the fuel system during refueling.

23. The system of claim 1, wherein the sensor is configured to perform periodic checks at predetermined intervals to confirm the continued presence of the refueling gun (116) in the fuel tank inlet (118) during the refueling process.

24. The system of claim 1, wherein the sensor additionally monitors the fuel level in the vehicle's fuel tank and automatically transmits a signal to the fuel pump (114) to stop refueling when a predetermined fuel level is reached.

25. The system of claim 1, wherein the sensor analyzes the fuel flow rate and compares it to historical data for the specific vehicle type to detect potential anomalies or overfilling attempts.

26. The system of claim 1, wherein the sensor is configured to detect flow of fuel from the refueling gun into the fuel tank inlet.

27. The system of claim 26, wherein the application on the mobile device is configured to monitor the duration of fuel flow into sent from the sensor.

28. The system of claim 27, wherein the application is configured to generate a notification in at least one of the following: fuel flow time below a predetermined minimum duration, fuel flow time above a predetermined maximum duration.

29. The system of claim 27, wherein the management server is configured to calculate an overall fuel flow time and assess whether the amount of the refueling transaction is consistent with the overall fuel flow time; and upon detecting that the overall fuel flow time is not consistent with the amount of the refueling transaction, flag the transaction as a potentially illegitimate transaction.

30. The system of claim 1, wherein the sensor utilizes ultrasonic technology to accurately detect the presence and position of the refueling gun (116) within the fuel tank inlet (118).

31. The system of claim 1, wherein the sensor employs image recognition to visually identify the type and compatibility of the inserted refueling gun (116).

32. The system of claim 1, wherein the sensor incorporates radio frequencyidentification (RFID) technology to uniquely identify the inserted refueling gun (116) and prevent unauthorized use.