WO2016108165A1

WO2016108165A1 - Anti-fraud authentication system and method

Info

Publication number: WO2016108165A1
Application number: PCT/IB2015/059995
Authority: WO
Inventors: Oren Levy; Bat-Chen HERCHKOVICH
Original assignee: 365 Technologies Ltd.
Priority date: 2014-12-29
Filing date: 2015-12-27
Publication date: 2016-07-07

Abstract

An anti-fraud authentication system and method comprising: at least one organization having a plurality of vehicles assigned to a plurality of users; a plurality of service stations; at least one system server comprising at least one users database, the system server running a server application configured to receive user data and provide purchase permissions; at least one point of sale at each one of the plurality of service stations, each one of the point of sale running a point of sale application configured to provide predetermined goods or services according to the permissions; and a plurality of electronic communication devices, each identified with one of the users, each one of the electronic communication devices running a user application configured to provide user data and receive a purchase code; wherein the server application communicates bi-directionally with the point of sale applications and with the user application.

Description

ANTI-FRAUD AUTHENTICATION SYSTEM AND METHOD

FIELD OF THE INVENTION

The present invention generally relates to fuel management systems and specifically to an anti-fraud authentication system and method. BACKGROUND

Fuel management systems which monitor fuel usage by vehicles and record the identity and other particulars of vehicles being fueled are known. The Fuelmat (Trade Mark) automated fuel management system is commercially available from Del Pak Systems Ltd, a subsidiary of Orpak industries (1983) Ltd. Former fuel management systems offered to use physical components mounted in the user's vehicle and on the fuel pump nozzle. These components are configured to authorize fueling using RF (radio frequency) verification between the vehicle component and the fuel pump nozzle component.

SUMMARY According to an aspect of the present invention there is provided a system for providing anti-fraud authentication to at least one organization having a plurality of vehicles assigned to a plurality of users, comprising: at least one system server comprising at least one database pertaining to the at least one organization, the at least one database storing user identifications, vehicle details and purchasing permissions, the system server running a server application configured to receive user data and provide permissions for purchasing predefined goods or services at a plurality of service stations; at least one point of sale (POS) at each one of the plurality of service stations, each one of the at least one point of sale running a point of sale application (POSA) configured to provide the predefined goods or services according to the permissions; and a plurality of electronic communication devices, each identified with one of the users, each one of the electronic communication devices running a user application configured to provide the user data and receive a purchase code; wherein the server application communicates bi-directionally with the point of sale applications and with the user applications.

The plurality of service stations may comprise a fuel station.

The at least one POS may comprise a fuel pump. The user data may comprise at least one of user identification, an odometer count, a captured image of a sticker mounted in a vehicle assigned to a user and a service station location.

The service station location may be provided automatically by the electronic

communication device's location sensor. The provided purchasing permissions may comprise authorized fuel amount.

According to another aspect of the present invention there is provided a method of providing anti-fraud authentication to at least one organization having a plurality of vehicles assigned to a plurality of users, comprising: providing at least one system server comprising at least one database pertaining to the at least one organization, the at least one database storing user identifications, vehicle details and purchasing permissions at a plurality of service stations; and at least one point of sale (POS) at each one of the plurality of service stations; using input means for providing user data to a user application running on an electronic communication device; providing the user data to a server application by the user application; checking by the server application the validity of the provided user data; and if the user data is valid - issuing by the server application a purchase code to the user; providing by the user the purchase code to a point of sale application; providing by the point of sale application the purchase code to the server application; receiving by the point of sale application purchasing permissions for the user; and providing predefined goods or services according to the permissions. The plurality of service stations may comprise a fuel company.

The at least one POS may comprise a fuel pump. The input means may comprise at least one of: typing, voice recognition and biometric identification.

The user data may comprise at least one of user identification, an odometer count, a captured image of a sticker mounted in a vehicle assigned to a user and a service station location.

The service station location may be provided automatically by the electronic

communication device's location sensor.

The checking of the validity of the user data may comprise authenticating the user of the electronic communication device. The authenticating the user may comprise comparing at least one of employee number, pin code and biometric identification to pre-stored values in the at least one database.

The purchasing permissions may comprise authorized fuel amount.

The checking of the validity of the user data may comprise authenticating the vehicle assigned to the user. The authenticating the vehicle may comprise comparing at least one captured image of a sticker mounted in the vehicle with at least one stored image of the sticker.

The authenticating the vehicle may comprise comparing at least one calculated parameter extracted from a sticker mounted in the vehicle with at least one stored calculated parameter extracted from a stored image of the sticker. The authenticating the vehicle may comprise comparing at least one captured and manipulated image of a sticker mounted in the vehicle with at least one stored manipulated image of the sticker.

According to another aspect of the present invention there is provided a system for providing anti-fraud authentication to at least one organization having a plurality of vehicles assigned to a plurality of users, comprising: at least one system server comprising at least one database pertaining to the at least one organization, the at least one database storing user identifications, vehicle details and purchasing permissions, the system server running a server application configured to receive user data and provide permissions for purchasing predefined goods or services at a plurality of service stations; a plurality of magnetic cards, each identified with a user and configured to provide the user data to a point of sale (POS); and at least one POS at each one of the plurality of service stations, each one of the at least one POS running a point of sale application (POSA) configured to provide the predefined goods or services according to the permissions; wherein the server application communicates bi-directionally with the point of sale applications. The plurality of service stations may comprise a fuel station.

The at least one POS may comprise a fuel pump.

The user data may comprise user identification.

The provided purchasing permissions may comprise authorized fuel amount.

According to another aspect of the present invention there is provided a method of providing anti-fraud authentication to at least one organization having a plurality of vehicles assigned to a plurality of users, comprising: providing at least one system server comprising at least one database pertaining to the at least one organization, the at least one database storing user identifications, vehicle details and purchasing permissions at a plurality of service stations; and at least one point of sale (POS) at each one of the plurality of service stations; providing user data to a point of sale application (POSA) by a user's magnetic card; providing the user data to a server application by the POSA; checking by the server application the validity of the provided user data; and if the user data is valid - issuing by the server application purchasing permissions for the user; receiving by the POSA the purchasing permissions for the user; and providing predefined goods or services according to the permissions.

The checking of the validity of the user data may comprise authenticating the user of the magnetic card. The authenticating the user may comprise comparing at least one of employee number, pin code and biometric identification to pre-stored values in a database.

The user data may comprise user identification and odometer count.

The method may further comprise providing service station location to the server application.

The service station location may be provided by the at least one POS.

The plurality of service stations may comprise a fuel station.

The purchasing permissions may comprise authorized fuel amount.

BRIEF DESCRIPTION OF THE DRAWINGS

For better understanding of the invention and to show how the same may be carried into effect, reference will now be made, purely by way of example, to the accompanying drawings.

With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of the preferred embodiments of the present invention only, and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the invention. In this regard, no attempt is made to show structural details of the invention in more detail than is necessary for a

fundamental understanding of the invention, the description taken with the drawings making apparent to those skilled in the art how the several forms of the invention may be embodied in practice. In the accompanying drawings:

Fig. 1 is a schematic view of the secured and monitored anti-fraud authentication system according to the present invention; Fig. 2 is a schematic view of the three applications used by the present invention and the communication between them;

Fig. 3 is a flowchart showing the process performed by the user application (UA) according to embodiments of the present invention; Fig. 4 is a flowchart showing the process performed by the Point Of Sale application (POSA) according to embodiments of the present invention;

Fig. 5 is a flowchart showing the process performed by the server application (SA) according to embodiments of the present invention;

Fig. 6 is a flowchart showing the purchasing process according to embodiments of the present invention;

Fig. 7 is a flowchart showing the data checking algorithm according to embodiments of the present invention;

Fig. 8 is an exemplary display of users' abnormalities;

Fig. 9A is a schematic view of the secured and monitored anti-fraud authentication system according to another embodiment of the present invention;

Fig. 9B is a flowchart showing the purchasing process using a magnetic card;

Fig. 10 demonstrates an example of a sticker;

Fig. 1 1 demonstrates another example of a sticker;

Fig. 12 demonstrates another example of a sticker; Fig. 13 demonstrates another example of a sticker;

Fig. 13A demonstrates a manipulation performed on a captured image of the sticker of Fig. 13; and

Fig. 13B demonstrates another manipulation performed on a captured image of the sticker of Fig. 13. DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of the components set forth in the following description or illustrated in the drawings. The invention is applicable to other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the

phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.

Many companies and organizations have vehicle fleets. One of the problems of managing such a fleet is to control and secure vehicle-related expenditures such as fueling, car wash, oil change, etc. in order to prevent frauds. This requires positive identification of the authorized service receiver and the vehicle at the Point of Sale (POS), e.g. fuel pump or cash register.

In the example of fueling, former solutions offered to use physical components mounted in the user's vehicle and on the fuel pump nozzle. These components are configured to authorize fueling using RF (radio frequency) verification between the vehicle component and the fuel pump nozzle component.

The present invention attempts to overcome the need of such physical components while providing an anti-fraud authentication system for all vehicle-related expenditures. In the present invention, identification of the user (the authorized service receiver) and the vehicle is done by a set of actions the user has to perform in order to prove that he has purchase authorization. The authorization criteria are defined by the paying entity (e.g. the user's company).

The term Km may refer hereinafter to any other distance unit such as mile, feet, yard and the like.

The term liter may refer hereinafter to any other volume unit such as gallon and the like. Fig. 1 is a schematic view of the secured and monitored anti-fraud authentication system 100 according to the present invention, comprising: a user 1 10 (e.g. an employee who is the authorized service receiver), an electronic communication device 120 (e.g. smartphone) running a user application (UA) 130, at least one system server 140, at least one service station 145 having at least one Point Of Sale - POS 150 (e.g. fuel station pump) and at least one company, organization, loyalty club and the like 160.

The system of the present invention offers to bind a plurality of vehicle-related service stations (e.g. fuel stations) in a wide deployment, in order to provide authenticated automated services. Organizations who wish to use this service communicate with the anti-fraud authentication system owner and establish a contract based on their needs and requirements.

According to embodiments of the invention, the anti-fraud authentication system owner may be a service provider (e.g. a fuel company) or an intermediate company which manages the connection between the plurality of service stations (e.g. fuel stations) and the organizations who wish to use this service, namely, each contract is established between the organization and the system owner.

The system server(s) 140 stores a database of authorized users' personal details and their personal purchase authorization rules (contract). Examples of user details may be: name, ID number, home address, work address, cellular number, e-mail address, vehicle license plate number, job description; vehicle type, model, color, engine volume, fueling tank volume, current odometer count and the like. Examples of purchase authorizations may be: fuel amount allocation, distance allocation per month (Km, miles, etc.), fuel type, authorized fueling hours, authorized fueling locations, car wash allocation, number of fuelings per day, week, month, etc. Users may also be divided into groups such as: shift employees, secretaries,

management and the like. For each group, a set of rules and conditions may be defined. For example, the shift employees group may be authorized to fuel once a day, up to 50 liters per fueling and up to 500 liters per month. According to embodiments of the invention, the process begins when the paying entity (e.g. an organization's fleet manager) opens a user card in the system server's database. The user card may comprise some or all the details and authorizations mentioned above. According to embodiments of the invention the user details may also comprise the fuel tank content at the moment of registration. Alternatively, the system may require the user to fill the tank to its full capacity in the first fueling. Both options enable the system to monitor the fuel amount in the tank and compare it with an amount predicted by the odometer count and the vehicle's fuel consumption. As soon as all the required details are provided, the system generates an activation code. This activation code is given to the user for him to be able to download the designated application to his mobile communication device (the same mobile number that was saved in the user's card) and activate it (the activation code is for one time use only). The user then registers to the application and is able to receive services according to his purchase authorizations. A user may also add a credit card number or a bank account number or permission to charge his paycheck in case of exceeded or extra charges.

According to embodiments of the invention, other people, such as family members may also drive the user's car. In such case the user may receive a number of activation codes (to fit the number of authorized people who may drive the car) in order for them to install the application on their devices (e.g. smartphones). Each one of the system server, the Point of Sale (POS) and the user communication device runs a unique application that enables it to perform the system requirements.

Fig. 2 is a schematic view of the three applications and the user and the communication between them.

Fig. 3 is a flowchart 300 showing the process performed by the user application (UA) according to embodiments of the present invention.

According to embodiments of the invention, when activated, in step 305 the UA receives identification details from the user (e.g. a user name and password). If the user's identification fails, it goes back to step 305. Otherwise, assuming the user is located in one of the vehicle-related service stations, in step 310, the user application (UA) derives the station's location from the user communication device (e.g. using the device's GPS) and sends it to the system server. In step 315 the UA receives from the server an indication whether the current station is authorized. If it is not authorized, in step 320, the UA informs the user that his location is not recognized as a location of one of the authorized service stations and may offer to navigate him to an authorized station, display a map of authorized stations, etc. Otherwise, in step 325, the UA receives from the user a predefined number (e.g. 3) of least significant digits of the vehicle's current odometer count and optionally a personal code (employee number, pin code, biometric identification such as fingerprint, etc.). In step 330, the UA sends these details to a data checking algorithm in the server (which will be explained in detail in conjunction with Fig. 7). If the check fails, in step 335 the process is terminated. Otherwise, in step 340, the UA receives a purchase code generated by the server and displays it on the display of the user communication device. At the end of the purchase process, in step 345, the UA may display the purchase details. In step 350, it waits for the user to approve the purchase details and terminates the process. Steps 345 and 350 are optional; the process may be terminated without the user's approval. According to embodiments of the invention, the user identification step, 305, may be done once, the first time a user activates the UA. From that time on, the process may begin from step 310.

In a case that the purchase is done by one of the authorized people other than the user (the contract owner), in step 345 the purchasing details may be sent to the contract owner's application as well (e.g. as a push notification).

According to embodiments of the invention, step 310 may be done manually by the user (marking on a map, address typing and the like).

Fig. 4 is a flowchart 400 showing the process performed by the Point Of Sale application (POSA) according to embodiments of the present invention.

According to embodiments of the invention, in step 405 the POSA receives a purchase code from the user (the same code the user received from the server in step 340 of Fig.3). In step 410 the POSA sends the code to the system server in order to identify the vehicle and the user's purchasing authorizations. In step 415, the POSA receives the user's purchasing authorizations from the server and authorizes a purchase according to it. When the purchase process is terminated (e.g. a fueling process), in step 420, the POSA sends the purchase details to the system server, optionally to the UA, optionally to the service station and optionally displays them on the POS display. In step 425, it waits for the user to approve the purchase details and terminates the process. The user's approval or disapproval does not affect the charge, the updating of the user's data and the like. The approval's purpose is to inform the user about the purchase details and to make sure that he approves them. In case that a user does not approve the purchase details, the system records the disapproval as an abnormality. According to embodiment of the invention, step 425 is optional and the process may be terminated without the user's approval.

In a case that the purchase is done by one of the authorized people other than the user (the contract owner), in step 420 the purchase details may be sent to the contract owner's application as well (e.g. as a push notification).

According to embodiment of the invention, in a case of a fueling process, in addition to the contract restrictions, the system may limit the fuel amount according to a predicted consumed fuel amount that is calculated according to the last odometer count, the present odometer count and the vehicle's known fuel consumption. Fig. 5 is a flowchart 500 showing the process performed by the server application (SA) according to embodiments of the present invention.

According to embodiments of the invention, in step 505, the SA receives from the UA the service station location. In step 510, it checks whether the location is of an authorized service station. If it isn't, in step 515, it sends a termination order to the UA. Otherwise, in step 520, it sends to the UA an authorization to proceed. In step 525, the SA receives from the UA a predefined number (e.g. 3) of least significant digits of the vehicle's current odometer count and optionally a personal code. In step 530, the received details are checked in the data checking algorithm. If the details are not verified, the process goes back to step 525 or aborts (after a predefined numbers of trials the application may abort the process). If the details are verified, in step 535, the SA sends a purchase code to the UA. In step 540, the SA receives from the POSA the purchase code. In step 545, according to the purchase code, it sends the user's authorizations back to the POSA. In step 550, the SA receives from the POSA the purchase details, stores them in the system server and updates the user's data (e.g. current fuel amount).

According to embodiments of the invention, a user who is driving into an unauthorized service station may get a notification about it and may be offered to navigate to one of the authorized service stations. Moreover, while driving, the user may see a list or a map of all the authorized service stations in the vicinity or in a requested distance and choose to navigate to one of them.

Fig. 6 is a flowchart 600 showing the purchasing process according to embodiments of the present invention.

In step 605, a user arrives at a service station, activates the UA and optionally provides his identification details (such as a user name and password, biometric identification and the like). In step 606, the process using, for example, the location capabilities (e.g. GPS) of the user's device, verifies the service station location and check that it is an authorized one. Alternatively, the service station location may be derived via Wi-Fi, beacon, etc. or may be entered manually by the user. If the service station is not one of the authorized service stations, the process is terminated and the UA may offer the user to navigate to one of the authorized service stations (step 660). Otherwise, in step 610 the user is prompted to provide and provides a predefined number (e.g. 3) of least significant digits of the vehicle's current odometer count and optionally a personal code (employee number, pin code, etc.). In step 615 the provided data is checked by the system's algorithm (Fig.7). If the check is successfully passed, in step 620 the system generates a purchase code and displays it on the user device 120. In step 625 the user inputs the purchase code into the POSA using Point Of Sale (e.g. fuel pump) input means, e.g. keyboard. In step 630 the POSA communicates with the system server and checks the user's purchase authorizations. In step 635 the POS enables the user to purchase (e.g. to fuel) according to the user's purchase authorizations. When the process is done, in step 640 the POSA sends the purchase details to the system server in order to update the user's data (e.g. current fuel amount), and optionally to the service station (e.g. fuel station), for monitoring purposes (e.g. monitor the amount of fuel used by a certain organization). In step 645 the user receives the purchase details and a notice that the process is terminated and approves them as explained above. If in step 615 the check didn't pass, the purchase is unauthorized, the process is terminated and the user receives a notice about it (step 650).

According to embodiments of the invention, step 645 is optional; the process may be terminated without the user's approval.

In a case that the purchase is done by one of the authorized people other than the user (the contract owner), in step 645 the purchasing details may be sent to the contract owner's application as well (e.g. as a push notification).

According to embodiments of the invention, the inputs to the purchase process (step 625) may also be provided by voice, using voice recognition modules in the UA and/or the POSA, touch or any other way known in the art.

According to embodiments of the invention, if the user is driving a different vehicle (the company's but not his), he may choose the vehicle from a list of authorized vehicles at the beginning of the process.

According to embodiments of the invention, if a user is having a problem with his communication device, has no reception or must make an emergency purchase, e.g. fuel an emergency fueling, he may use an emergency code at the POS that will enable him to perform a minimal required purchase. For example, in case of emergency fueling, the system may authorize a predetermined amount of fuel. A flag will rise in such occasion for the supervisor to notice. According to embodiments of the invention, in case that a user is purchasing in a station that is not one of the authorized stations, the UA may enable him to provide the purchasing details. In case of fuel purchase, this information is important in order to prevent a gap in the recorded odometer count (at the server) that might be interpreted as an abnormality. In such a case the UA may prompt the user to provide the vehicle's odometer count (the whole number) and the amount of fuel that was purchased. In addition, the user may have to provide this fueling receipt to his organization (e.g. to the supervisor). If a user wishes to be reimbursed for this fueling money by his organization (in case that it is allowed), he will have to provide the fueling details that were mentioned above in real time, namely, at the service station and to provide the receipt to his organization, thus enabling the supervisor to compare between the fueling amount that was provided by the user when he was in the station and the amount that is written on the receipt. A second comparison may be between the service station location that is printed on the receipt and the fuel station location that was derived from the user's device in real time (when he was in the station).

According to embodiments of the invention, during the process the system checks and records the service station location, the user device location in step 620 and the user device location in step 645. These checks assist to validate that the user himself (or at least his communication device) is at the service station.

Fig. 7 is a flowchart 700 showing the data checking algorithm according to

embodiments of the present invention. In step 705, the algorithm receives the data provided by the user (a predefined number (e.g. 3) of least significant digits of the vehicle's current odometer count and optionally a personal code (employee number, pin code, etc.)). In step 710, the algorithm checks if the user's personal code is correct and if it isn't, in step 715 the algorithm decreases by one an incorrect counter. The incorrect counter is a predetermined number of mistakes that a user is allowed to make. In step 720 the algorithm checks if the counter equals zero, namely, no more mistakes are allowed. If it is, in step 725 it generates a "failed" message. Otherwise, the algorithm goes back to step 705. If in step 710 the user's personal code is correct, in step 730 the algorithm checks if the provided odometer count (POC) is smaller than or equal to the last recorded odometer count (LROC). If it is, the algorithm goes to step 725 and generates a "failed" message. Otherwise, the odometer count is bigger than the last recorded odometer count. In step 735 the algorithm checks if the provided odometer count is dramatically bigger than the last recorded odometer count. If it is, in step 740 the algorithm raises a B_flag and generates a "passed" message (step 745). Otherwise it generates a "passed" message (step 745).

The BJlag is used to indicate abnormalities and will be used and explained below.

In case that the dramatically bigger odometer count exceeds the reasonable odometer count, the system may limit the fueling amount to the maximum reasonable amount. For example, if at the last fueling a user had 30 liters in the tank and the odometer count was 200, and assuming that the vehicle's fuel consumption is 1 liter per 10 kilometers and the tank capacity is 50 liters, the maximum reasonable odometer count should be 400, hence, the system may limit the authorized fuel amount to 20 liters (50-30=20). Steps 710 - 720 are optional. The process may go directly from step 705 to step 730.

According to embodiments of the invention, once in a while, randomly or according to the number of flags a user has been assigned, the system may perform additional checks in order to make sure that the user is who he claims to be and the vehicle is an authorized vehicle. The additional checks may be: providing the most significant digits\combination of digits\whole vehicle's current odometer count, capturing a photo of the front of the vehicle using the user's device (in real time via the application, the user won't be able to upload a photo, e.g. from his photo album), capturing a photo of the odometer and the like. Only if the user passes these additional checks is the purchasing authorized. Each user has a user card in the system server database where all of his personal details, purchase authorizations and purchase history are kept. The purchase history comprises all the purchase details including the odometer counts, purchase dates and hours, locations and flags the user may have. The system generates reports, periodically or by request, using these details and checks if a user has abnormalities. Quantitative abnormalities may comprise: odometer count that is

smaller\equal\dramatically bigger than the last recorded odometer count, odometer count that is smaller\bigger\dramatically bigger than the predicted odometer count (the predicted odometer count is determined by the system according to the vehicle's known fuel consumption and the last odometer count); fueling up to the limit of the maximal fueling permission, fueling a few times a day (though this may be limited by the purchase authorizations), fueling fixed amounts of fuel, high frequency small amounts fueling, fixed differences between odometer counts and the like. Behavioral abnormalities may comprise: purchasing during working hours (assuming the user is not supposed to drive his vehicle during these hours), purchasing on weekdays in a service station that is not on the route to work, fueling more than an authorized number of times during the weekend, etc.

Based on the above, the system may categorize each user in a group. According to embodiments of the present invention there are three groups:

- Red - dramatic abnormalities.

- Yellow - borderline abnormalities.

- Green - no abnormalities.

These groups assist a supervisor to inspect each user and consider further actions. If a supervisor decides that a specific user's abnormality is not an abnormality, namely, for this specific user there is an exception(s), he may mark this abnormality as "Okay" and the system will no longer address it.

It would be appreciated that the three groups are provided here only as one example of an embodiment of the invention that is not limited to this example and more than three or even two groups may be used.

Fig. 8 is an exemplary display of users' abnormalities.

The system may also perform statistical checks periodically. The system may "learn", over time, the "normal" behavior of a user and may inform the supervisor when an unusual behavior occurs. For example, if a user is driving an average of X Kms per week, and in a certain week he drives X+Y Kms (e.g. Y>0.3X), the system may inform the supervisor or a fraud analyst about it. The present invention is described hereinabove mainly in relation to fuel purchasing where the POS is a fuel pump. According to embodiments of the present invention, the authentication process may be used in order to enable purchase of other services such as car wash, products such as motor oil and the like. In these embodiments, the user receives from the server a purchase code which allows him to purchase services and\or products according to his contract. The user provides the purchase code to a Point of Sale (POS) running a POS application (POSA as described above) to complete the purchase. The system of the present invention may also enable vehicle-related service stations to offer personalized service to each user, for example, a tire change, according to the user's odometer count (every X Km).

The system may also enable to purchase insurance based on the recorded authorized service receiver's behavior.

According to embodiments of the present invention, an On-Board

Diagnostics component (e.g. ELM327 OBD2 available from http://elmelectronics.com) may be installed in the vehicle. The OBD2 component is connected to the vehicle's computer and may derive from it the vehicle's license plate number, the amount of fuel in the tank, the odometer count, the average driving speed and the like. The OBD2 may then broadcast this data using wireless communication such as Bluetooth or Wi-Fi to the user application and\or the system's server. This data may assist the system to validate and double check the data received from the UA and/or from the POS.

In case that the vehicle's computer comprises wireless communication capabilities, the vehicle's license plate number, the amount of fuel in the tank, the odometer count, the average driving speed and the like may be broadcasted by it to the user application and\or to the system's server directly. This data may assist the system to validate and double check the data received from the UA and/or from the POS.

According to embodiments of the present invention, the electronic communication device may be replaced with a magnetic card.

Fig. 9A is a schematic view of another embodiment of the secured and monitored anti- fraud authentication system 100A according to the present invention, comprising: a user 1 10A (e.g. an employee who is the authorized service receiver), a magnetic card 120A, at least one system server 140A, at least one service station 145A having at least one Point Of Sale - POS 150A (e.g. fuel station pump) and at least one company, organization, loyalty club and the like 160A. Fig. 9B is a flowchart 900 showing the purchasing process using a magnetic card.

In step 910 the user swipes his magnetic card in one of the authorized service stations' Points of Sale, provides identification details, such as, license plate number, employee number, user name and password and the like and a predefined number (e.g. 3) of least significant digits of the vehicle's current odometer count. In step 915 the provided data is checked by the system's algorithm (Fig.7). If the check is passed successfully, in step 920 the POSA communicates with the system server and checks the user's purchase authorizations. In step 925 the POS enables the user to purchase. When the process is done, in step 930 the POSA sends the purchase details to the system server in order to update the user's data (e.g. current fuel amount), and optionally to the service station, for monitoring purposes (e.g. monitor the amount of fuel used by a certain

company\organization). In step 935 the user receives the purchase details on the POS display, approves them and the process is terminated. If in step 915 the check didn't pass, the purchasing is unauthorized, the process is terminated and the user receives a notification about it (step 940). According to embodiments of the present invention, step 935 is optional; the process may be terminated without the user's approval.

According to embodiments of the present invention, another way to identify the user's vehicle may be by capturing by the user, using a camera of the user's mobile device running the UA of the present invention, a unique sticker mounted in a visible and accessible location in the vehicle, thus enabling the UA to validate or invalidate the sticker by comparing it to a stored image(s) of the sticker captured when the sticker was installed.

In the installation process, the unique sticker is installed, captured and saved in the system's DB. A number of different images, each with the focal square of the camera directed towards a different location in the sticker, may be captured and saved.

Alternatively or additionally, the system may perform manipulations on the captured image(s) provided by the user and save them as well. Each sticker has different characteristics which distinguish it from others. Fig. 10 demonstrates an example of a sticker 1000. The exemplary sticker comprises a plurality of small quadrangles, a larger quadrangle and marked corners 1010A-1010D of a quadrangle which represents the camera's focal square. In the installation process of this exemplary sticker, the sticker is captured and saved. According to embodiments of the invention, the locations and distances of the small quadrangles from the larger quadrangle which are unique to each sticker are saved as well. According to

embodiments of the invention, the system may save triangulation relations between different combinations of three quadrangles. According to embodiments of the invention, the system may perform manipulations on the captured image, e.g. rotation, and save the manipulated image(s). According to embodiments of the invention, the sticker may be captured a number of times with the focal square of the camera directed towards different locations in the sticker.

When the user is prompted to identify his vehicle, he captures an image(s) of the sticker while his camera's focal square and the sticker's square 1010 coincide. The system may compare the captured image to the one saved in the DB, perform a manipulation on the captured image and compare it to the corresponding manipulated stored image and/or compare the distances, locations or triangulation relations in the captured image to those in the stored image. Using these comparisons the system validates or invalidates the user's vehicle.

Fig. 1 1 demonstrates another example of a sticker 1 100. The exemplary sticker comprises four different colored quadrangles 1 101 , 1 102, 1 103 and 1 104, four marks 1 120, 1 130, 1 140 and 1 150 and marked corners 1 1 10A-1 1 10D of a quadrangle which represent the camera's focal square. In the installation process of this exemplary sticker, the sticker is captured and saved. According to embodiments of the invention, the locations and distances of the marks 1 120, 1 130, 1 140 and 1 150 from the colored quadrangles 1 101 , 1 102, 1 103 and 1 104 which are unique to each sticker are saved as well. According to embodiments of the invention, the sticker may be captured a number of times with the focal square of the camera directed towards different locations in the sticker, e.g. different colored quadrangle. According to embodiments of the invention, the system may perform manipulations on the captured image, e.g. rotation, and save the manipulated image(s).

When the user is prompted to identify his vehicle, he may be instructed by the UA to capture the sticker while his camera's focal square and the marked corners 1 1 10A- 1 1 10D coincide. Alternatively or additionally the UA may instruct the user to capture the sticker when one of the colored quadrangles 1 101 , 1 102, 1 103 and 1 104 is in the focal square of the camera. The system may compare the captured image to the one saved in the DB, perform a manipulation on the captured image and compare it to the corresponding manipulated stored image and/or compare the distances and/or locations in the captured image to those in the stored image. Using these comparisons the system validates or invalidates the user's vehicle accordingly. Fig. 12 demonstrates another example of a sticker 1200. In this example, the

uniqueness of the sticker is the exact locations of the stars 1210 and 1220. In the installation process the person who installs the sticker creates these stars using a perforator and captures the image to be stored in the system's DB. The star shape is just an example for the purpose of demonstration, any shape may be perforated. The system compares the captured image to the one stored in the DB and validates or invalidates the user's vehicle accordingly.

Fig. 13 demonstrates another example of a sticker 1300. The exemplary sticker comprises three marks 1310, 1320 and 1330 mounted on a virtual invisible circle 1340 and a mark 1360 mounted in square 1350 representing the camera's focal square. In the installation process of this exemplary sticker, the sticker is captured and saved. According to embodiments of the invention, the locations and distances of the marks 1310, 1320 and 1330 from the center of the square 1350 which are unique to each sticker are saved as well. According to embodiments of the invention, the system may perform manipulations on the captured image, e.g. rotate the three marks 1310, 1320 and 1330 on the virtual invisible circle 1340, and save the manipulated image(s). When the user is prompted to identify his vehicle, he captures an image of the sticker while his camera's focal square and the square 1350 coincide. According to

embodiments of the present invention, the system may compare the captured image(s) provided by the user with the captured image(s) stored in the DB as they are.

Alternatively or additionally, the system may perform manipulations on the captured image provided by the user and compare it to a manipulated image stored in the DB. Using these comparisons the system validates or invalidates the user's vehicle.

Fig. 13A demonstrates a manipulation performed on a captured image of the sticker of Fig. 13. In this example, the system rotates the three marks 1310, 1320 and 1330 mounted on the virtual invisible circle 1340, 15 degrees clockwise. The square 1350 and the mark 1360 stay in place. The system compares the captured and manipulated image to the one stored in the DB and/or compares the distances between the marks and validates or invalidates the user's vehicle accordingly.

Fig. 13B demonstrates another manipulation performed on a captured image of the sticker of Fig. 13. In this example, the system rotates the three marks 1310, 1320 and 1330 mounted on the virtual invisible circle 1340, 50 degrees counterclockwise. The square 1350 and the mark 1360 stay in place. The system compares the captured and manipulated image to the one stored in the DB and/or compares the distances between the marks and validates or invalidates the user's vehicle accordingly. According to embodiments of the present invention, the identification process described in conjunction with Figs. 10-13B may be performed in addition or instead of the identification processes described above.

It will be appreciated by persons skilled in the art that the present invention is not limited to what has been particularly shown and described hereinabove. Rather the scope of the present invention is defined by the appended claims and includes combinations and sub-combinations of the various features described hereinabove as well as variations and modifications thereof which would occur to persons skilled in the art upon reading the foregoing description.

Claims

1 . A system for providing anti-fraud authentication to at least one organization

having a plurality of vehicles assigned to a plurality of users, comprising:

at least one system server comprising at least one database pertaining to said at least one organization, said at least one database storing user identifications, vehicle details and purchasing permissions, said system server running a server application configured to receive user data and provide permissions for purchasing predefined goods or services at a plurality of service stations;

at least one point of sale (POS) at each one of said plurality of service stations, each one of said at least one point of sale running a point of sale application (POSA) configured to provide said predefined goods or services according to said permissions; and

a plurality of electronic communication devices, each identified with one of said users, each one of said electronic communication devices running a user application configured to provide said user data and receive a purchase code; wherein said server application communicates bi-directionally with said point of sale applications and with said user applications.

2. The system of claim 1 , wherein said plurality of service stations comprises a fuel station.

3. The system of claim 2, wherein said at least one POS comprises a fuel pump.

4. The system of claim 1 , wherein said user data comprises at least one of user identification, an odometer count, a captured image of a sticker mounted in a vehicle assigned to a user and a service station location.

5. The system of claim 4, wherein said service station location is provided

automatically by said electronic communication device's location sensor.

6. The system of claim 2, wherein said provided purchasing permissions comprise authorized fuel amount.

7. A method of providing anti-fraud authentication to at least one organization

having a plurality of vehicles assigned to a plurality of users, comprising:

providing at least one system server comprising at least one database pertaining to said at least one organization, said at least one database storing user identifications, vehicle details and purchasing permissions at a plurality of service stations; and

at least one point of sale (POS) at each one of said plurality of service stations;

using input means for providing user data to a user application running on an electronic communication device;

providing said user data to a server application by said user application;

checking by said server application the validity of said provided user data; and if said user data is valid - issuing by said server application a purchase code to said user;

providing by said user said purchase code to a point of sale application;

providing by said point of sale application said purchase code to said server application;

receiving by said point of sale application purchasing permissions for said user; and

providing predefined goods or services according to said permissions.

8. The method of claim 7, wherein said plurality of service stations comprises a fuel company.

9. The method of claim 8, wherein said at least one POS comprises a fuel pump.

10. The method of claim 7, wherein said input means comprise at least one of:

typing, voice recognition and biometric identification.

1 1 . The method of claim 7, wherein said user data comprises at least one of user identification, an odometer count, a captured image of a sticker mounted in a vehicle assigned to a user and a service station location.

12. The method of claim 1 1 , wherein said service station location is provided

automatically by said electronic communication device's location sensor.

13. The method of claim 7, wherein checking the validity of said user data comprises authenticating said user of said electronic communication device.

14. The method of claim 13, wherein authenticating said user comprises comparing at least one of employee number, pin code and biometric identification to pre- stored values in said at least one database.

15. The method of claim 8, wherein said purchasing permissions comprise authorized fuel amount.

16. The method of claim 7, wherein checking the validity of said user data comprises authenticating said vehicle assigned to said user.

17. The method of claim 16, wherein authenticating said vehicle comprises

comparing at least one captured image of a sticker mounted in said vehicle with at least one stored image of said sticker.

18. The method of claim 16, wherein authenticating said vehicle comprises

comparing at least one calculated parameter extracted from a sticker mounted in said vehicle with at least one stored calculated parameter extracted from a stored image of said sticker.

19. The method of claim 16, wherein authenticating said vehicle comprises

comparing at least one captured and manipulated image of a sticker mounted in said vehicle with at least one stored manipulated image of said sticker.

20. A system for providing anti-fraud authentication to at least one organization

having a plurality of vehicles assigned to a plurality of users, comprising:

at least one system server comprising at least one database pertaining to said at least one organization, said at least one database storing user

identifications, vehicle details and purchasing permissions, said system server running a server application configured to receive user data and provide permissions for purchasing predefined goods or services at a plurality of service stations;

a plurality of magnetic cards, each identified with a user and configured to provide said user data to a point of sale (POS); and

at least one POS at each one of said plurality of service stations, each one of said at least one POS running a point of sale application (POSA) configured to provide said predefined goods or services according to said permissions;

wherein said server application communicates bi-directionally with said point of sale applications.

21 . The system of claim 20, wherein said plurality of service stations comprises a fuel station.

22. The system of claim 21 , wherein said at least one POS comprises a fuel pump.

23. The system of claim 20, wherein said user data comprises user identification.

24. The system of claim 21 , wherein said provided purchasing permissions comprise authorized fuel amount.

25. A method of providing anti-fraud authentication to at least one organization

having a plurality of vehicles assigned to a plurality of users, comprising:

providing user data to a point of sale application (POSA) by a user's magnetic card;

providing said user data to a server application by said POSA;

checking by said server application the validity of said provided user data; and if said user data is valid - issuing by said server application purchasing permissions for said user;

receiving by said POSA said purchasing permissions for said user; and providing predefined goods or services according to said permissions.

26. The method of claim 25, wherein checking the validity of said user data

comprises authenticating said user of said magnetic card.

27. The method of claim 26, wherein authenticating said user comprises comparing at least one of employee number, pin code and biometric identification to pre- stored values in a database.

28. The method of claim 25, wherein said user data comprises user identification and odometer count.

29. The method of claim 25, further comprising providing service station location to said server application.

30. The method of claim 29, wherein said service station location is provided by said at least one POS.

31 . The method of claim 25, wherein said plurality of service stations comprises a fuel station.

32. The method of claim 31 , wherein said purchasing permissions comprise

authorized fuel amount.