WO2015048015A1 - Appariement automatisé de produits de paiement et dispositifs de mobile à mobile - Google Patents

Appariement automatisé de produits de paiement et dispositifs de mobile à mobile Download PDF

Info

Publication number
WO2015048015A1
WO2015048015A1 PCT/US2014/056974 US2014056974W WO2015048015A1 WO 2015048015 A1 WO2015048015 A1 WO 2015048015A1 US 2014056974 W US2014056974 W US 2014056974W WO 2015048015 A1 WO2015048015 A1 WO 2015048015A1
Authority
WO
WIPO (PCT)
Prior art keywords
vehicle
location
transaction
telematics
card
Prior art date
Application number
PCT/US2014/056974
Other languages
English (en)
Inventor
Max L. JOHNSON
Original Assignee
Fleetcor Technologies Operating Company, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/054,279 external-priority patent/US9563893B2/en
Application filed by Fleetcor Technologies Operating Company, Llc filed Critical Fleetcor Technologies Operating Company, Llc
Publication of WO2015048015A1 publication Critical patent/WO2015048015A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3224—Transactions dependent on location of M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/401—Transaction verification
    • G06Q20/4015—Transaction verification using location information
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/308—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using the Internet of Things
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station

Definitions

  • This invention relates generally to computer-implemented data computation and, more particularly, to computer-assisted automatic pairing or linking of devices and/or devices to payment methods.
  • Businesses may provide its employees with payment products that can be used by the employees to cover approved expenses associated with using various assets associated with the businesses.
  • a business may own or lease a plurality of vehicles for various purposes, such as goods transportation, fulfilling delivery orders, and/or employee travel related to the business.
  • the business may cover expenses that are associated with the vehicles, such as the fuel cost and/or the maintenance cost of the vehicles.
  • the business may furnish the drivers of the vehicles with payment products, such as financial services cards and/or fuel cards that may be used by the drives to cover the approved expenses.
  • Co-relating and cross-checking information provided by the payment products associated with the employees and the assets of the business used by the employees can provide greater business insights, such as asset usage pattern of the employee, payment card and asset usage statistics associated with the employee, fraudulent or unauthorized usage statistics, and so on.
  • co-relating and cross-checking information provided by mobile phones associated with the employees and the assets of the business used by the employees can provide further business insights.
  • a quick and easy co- relation and cross-checking of information associated with the payment product, mobile phone and/or asset can be achieved by pairing or linking each payment product of an employee and/or mobile phone of the employee with the respective one or more assets used by the employee.
  • the present disclosure can address the above-described needs by an automated pairing of (i) payment products and mobile to mobile devices (M2M) (e.g., mobile phones, tablets, vehicle telematics device, etc.) and/or (ii) M2M devices to one another.
  • M2M mobile to mobile devices
  • the present disclosure utilizes one or more programmed computers to automatically pair financial services cards and/or mobile computing devices of a driver with a vehicle associated with the driver.
  • a driver of a vehicle may be provided a financial service card for covering expenses incurred in association with the vehicle, such as expenses associated with purchase of fuel, vehicle maintenance, etc.
  • the vehicle may be equipped with a telematics device that is configured to collect and transmit vehicle related data, such as a location of the vehicle, a time and date at which the location was recorded, diagnostics associated with the vehicle, etc., to a vehicle database.
  • vehicle database may include vehicle related data associated with one or more vehicles.
  • a computer receives card transaction data that is associated with the transaction made using a financial services card.
  • the card transaction data includes at least a time, a date, and a location associated with the transaction.
  • the card transaction data can include card number, encrypted card number, transaction type, purchased product, product type (unleaded, leaded, premium fuel, etc.), price of purchased product, transaction amount, and so on, without departing from a broader spirit of this disclosure.
  • the computer Responsive to a substantial match of the location associated with the transaction with a location of at least one of the one or more vehicles at said time and date associated with the transaction, the computer associates (pairs) the financial services card with the vehicle whose location substantially matched the location of the transaction. However, if the comparison results in a match of the financial services card with more than one vehicle, then, the computer re -runs the comparison using card transaction data corresponding to subsequent transactions made using the financial services card. In one example, the comparison may be re-run until the pairing can be narrowed down to a paring between one financial services card and one vehicle for a given transaction time and date associated with the financial services card. In another example, the comparison may be re-run for a pre-determined number of times.
  • the re-running of the comparison using card transaction data corresponding to subsequent transactions is also used to reinforce an initial association (pairing) of the financial services card and the vehicle.
  • the pairing can also be reinforced by comparing historical card transaction data of the financial services card with historical vehicle related data associated with the matched vehicle.
  • a computer receives a card transaction data corresponding to a financial services card Y.
  • the received card transaction data indicates that a transaction using the financial services card Y was made at location X at 5.30 pm on Monday, August 1, 2004.
  • a vehicle database may include vehicle related information associated with a plurality of vehicles.
  • the vehicle related data is received from telematics device equipped in each of the plurality of the vehicles, e.g., 'n' vehicles.
  • the computer compares the card transaction data to the vehicle related data stored in the vehicle database to determine if any of the 'n' vehicles were present at location X or within a radius of location X at 5.30 pm on Monday, August 1, 2004.
  • the computer determines that vehicle Z was at location X at 5.30 pm on Monday, August 1, 2004, then, the computer pairs financial services card Y with vehicle Z. Further, to reinforce the pairing, the computer re-runs the comparison with card transaction data associated with the next transaction, e.g., transaction at 6.30 pm, provided the next transaction with financial services card Y occurs at 6.30 pm.
  • Pairing of financial services cards to the vehicle can provide insight both card usage and vehicle usage patterns. For example, if the financial services card is a fuel card, by matching a unique location history of a vehicle via telematics data with a unique transaction history of a fuel card, it can then be determined that this fuel card (or unique set of fuel cards) is associated with a unique vehicle, and are therefore matched during that window of time. This vehicle related information can then be combined with transaction information to give greater insight into fueling events and vehicle and driver performance. For example, the miles traveled by the vehicle can be combined with the gallons pumped into the vehicle, resulting in a 'true miles per gallon' figure that can be calculated for the vehicle.
  • a mobile computing device can be associated with a vehicle based on the location of the vehicle obtained from the telematics device associated with the vehicle and a location of the mobile computing device obtained either from within or outside the mobile computing device.
  • the location of the vehicle at a given time and date is compared with the location of the mobile computing device at said time and date to determine if they substantially match.
  • the mobile computing device is associated (paired) with the vehicle for said time and date. Assuming that a phone number associated with the mobile computing device can be linked to a driver or worker, then it follows that this driver or worker can be matched to a specific vehicle during specific times.
  • This paired information can be combined with other information, such as how the vehicle was driven or operated, to provide a fleet manager with visibility into a particular driver that is responsible for certain driving or purchase behaviors.
  • the computer In addition to pairing a vehicle to a payment product and/or a device associated with a driver of the vehicle, the computer generates and outputs a report for presentation to a used based on the pairing of the vehicle to the payment product and/or the device associated with a driver of the vehicle.
  • the computer can include an output engine or interface for outputting reports for presentation of one or more analysis results based on the paired vehicle and payment product and/or paired vehicle and the device associated with a driver of the vehicle.
  • the report may be generated in text and/or graphical formats.
  • Example analysis reports can include, but are not limited to, a listing of vehicles with their respective payment cards or devices of drives to which they are paired, alerts identifying fraudulent usage of the payment product, a real-time gas mileage of the vehicle, a driving pattern of the vehicle, maintenance of the vehicle, and so on.
  • the computer can output the report in an electronic form, in a printed form on paper, or as electronic information transmitted by a computer via a communication network for presentation at a location remote from the physical location of the computer that generates the report.
  • Figure 1 illustrates an example system for automated pairing of mobile to mobile devices with other mobile to mobile devices and/or with payment products, according to certain exemplary embodiments.
  • Figure 2 illustrates an example functional block diagram of the telematics server illustrated in Figure 1, according to certain exemplary embodiments.
  • Figures 3A and 3B are flow charts that illustrate a process of automated pairing of mobile to mobile devices with payment products, according to certain exemplary embodiments.
  • Figures 4A and 4B are flow charts that illustrate a process of automated pairing of mobile to mobile devices with other mobile to mobile devices, according to certain exemplary embodiments.
  • M2M devices may generally refer to any appropriate mobile data processing device.
  • M2M devices may include mobile phones, smart phones, tablets, and vehicle telematics devices. Each M2M device may have wireless communication capability for transmission or reception of data via wireless networks.
  • the term 'telematics device' as used herein may generally refer to any appropriate device that is adapted to send, receive, and store information via telecommunication devices.
  • the telematics device may be configured to send information associated with a vehicle, such as location of the vehicle, a heading direction of the vehicle, speed of the vehicle, distance traveled by the vehicle, and so on.
  • the telematics device may be configured to store and/or send data associated with a condition of the vehicle.
  • the telematics device may be configured to receive the fuel level data of the vehicle from a vehicle bus and/or communicate the received fuel level data over a telecommunication network.
  • the telematics device may be adapted to be used with the vehicle.
  • the telematics device may be an independently purchasable device that is configured to be attached to and/or detached from the vehicle as desired.
  • the telematics device may be attached to an onboard diagnostics (OBD) port of the vehicle to receive data associated with the vehicle from the vehicle bus.
  • OBD onboard diagnostics
  • the telematics device may be integrated with the vehicle.
  • the telematics device may be a Global Positioning System technology integrated with computers and mobile communications technology present in automotive navigation and internal network systems, such as OnStar®.
  • the term 'vehicle bus,' as used herein may generally refer to any appropriate internal communications network of a vehicle that interconnects components inside the vehicle.
  • the internal communications network of the vehicle may allow micro controllers and devices such as engine control unit, transmission control unit, anti-lock breaking system, body control modules, other sensors, etc., that are already present in the vehicle to communicate with each other within the vehicle.
  • the internal communication network, the micro controller, and the devices of the vehicle may operate in concert to collect, handle, and maintain any appropriate data associated with a condition of the vehicle, such as fuel level data of the vehicle, brake fluid level, engine status, and so on.
  • the different vehicle bus protocols may include, but are not limited to, Controller Area Network (CAN), Local Interconnect Network (LIN), Domestic Digital Bus (D2B), FlexRay, DC-BUS, IEBus, Media Oriented Systems Transport (MOST), SMARTwireX, and so on.
  • CAN Controller Area Network
  • LIN Local Interconnect Network
  • D2B Domestic Digital Bus
  • FlexRay DC-BUS
  • IEBus IEBus
  • MOST Media Oriented Systems Transport
  • SMARTwireX and so on.
  • the data collected, handled, and/or maintained by the vehicle bus can be obtained by connecting to the vehicle bus via an on board diagnostics (OBD) connector.
  • OBD on board diagnostics
  • the term 'financial services card,' as used herein may generally refer to any appropriate payment card.
  • the financial services card may include, but is not limited to, debit cards, credit cards, fuel cards, gift cards, and so on.
  • financial services cards may not be exhaustive and may include any appropriate card that can be used by a cardholder, and accepted by a merchant to make a payment for a purchase or in payment of some other obligation.
  • the financial services card may be a physical card, such as a magnetic stripe card.
  • the financial services card may be a smart card.
  • the fuel card may be an NFC based card, RFID based card, QR code based cards, and so on.
  • the financial services card may be software implementation, such as a mobile payment card stored in a mobile wallet wherein the payment is performed via a mobile computing device.
  • the term 'card transaction data,' as used herein may generally refer to any appropriate data associated with the usage of the financial services card.
  • the financial services card transaction data can include information representative of the location at which the financial services card was used, the time and date at which at the financial services card was used, a quantity of an item purchased using the financial services card, and so on.
  • financial services card transaction data are not exhaustive and that the financial services card transaction data may include or may include some of the above mentioned data.
  • the financial services card transaction data may include any appropriate number and type of additional information associated with purchase using the financial services card.
  • the term 'telematics information,' as used herein may generally refer any appropriate data associated with a vehicle.
  • the telematics information may be received from a telematics device installed in the vehicle and can include, but is not limited to, location of the vehicle, an amount of fuel present in the fuel tank of the vehicle, an oil level of the vehicle, a performance of the engine, a maintenance and service of the vehicle, a tire pressure of the vehicle, a condition of the windshield of the vehicle (broken), a broken taillight, an issue with the alignment of the wheels of a vehicle, an issue with a headlight of a vehicle, an issue associated with a license plate of the vehicle, an issue with the breaks of the vehicle, and so on.
  • Each data received from the telematics device may be time stamped, wherein the timestamp associated with the received data may be indicative of a time and date at which the data was obtained or recorded by the telematics device.
  • a computer is configured to receive transaction data that includes at least a location of the location associated with a transaction made using a payment card, such as a fuel card, and a unique identifier associated with the fuel card.
  • the computer determines the vehicle, the driver of the vehicle, and/or the telematics device of the vehicle (collectively referred to herein 'pairing elements') to which the transaction data is associated.
  • the computer may compare the unique identifier associated with the fuel card against an association table stored in a database.
  • the association table may include a mapping of the unique identifier associated with the fuel card to a unique identifier of one or more of the pairing elements.
  • the association table may be generated by the computer responsive to pairing the fuel card with one or more of the pairing elements.
  • the fuel card may be paired with one or more of the pairing elements initially when a manager provides the fuel card to the driver of the vehicle, wherein the pairing may be done automatically and/or manually by either the driver or the manager.
  • the fuel card may be paired with one or more the pairing elements on the fly. That is, the pairing may not be done initially. Rather, the pairing occurs automatically on the go without any manual entries or intervention.
  • the current application describes an automated pairing of a payment product (e.g., fuel card, debit card, credit card, etc.) and/or a mobile computing device (e.g., phone, laptop, tablet, pager, etc.) with a vehicle.
  • a payment product e.g., fuel card, debit card, credit card, etc.
  • a mobile computing device e.g., phone, laptop, tablet, pager, etc.
  • pairing the fuel card may include mapping a unique identifier of the fuel card with a unique identifier associated with either the computing device of the driver, the vehicle, and/or the telematics device.
  • the fuel card number may be mapped to a Vehicle Identifier Number (VIN) associated with the vehicle.
  • VIN Vehicle Identifier Number
  • the fuel card number may be mapped to a unique device number, such a manufacturer embedded code associated with the telematics device.
  • the account number associated with the fuel card may be mapped to an International Mobile Station Equipment Identifier (IMEI) number or phone number of a smart phone associated with the driver.
  • IMEI International Mobile Station Equipment Identifier
  • one or more identifiers of the fuel card may be mapped to a unique identifier (many-to-one) associated with either the computing device of the driver, the vehicle and/or the telematics device to account for the difference in transaction data based on the different POS devices.
  • Pairing a payment card such as the fuel card with a vehicle, a telematics device associated with the vehicle, and/or the computing device associated with the driver of the vehicle can be used to detect a fraudulent usage of the payment card, determining a driving pattern of the driver, determining a real-time gas mileage of the vehicle, and so on.
  • An example embodiment for automated pairing of a payment product and/or a mobile computing device with a vehicle includes a computer that is configured to receive a location associated with a transaction made using the payment product, a location of the mobile computing device, and a location of the vehicle obtained from a telematics device associated with the vehicle. Data that provides location is time stamped with a time and date at which the location was obtained or recorded. Upon receiving the location, and time and date associated with the location, a computer compares the location of the transaction and/or the location of the mobile computing device with the location of the vehicle at the time and date associated with the location of the transaction and/or the mobile computing device, respectively.
  • the computer pairs the vehicle with the payment product and/or the mobile computing device, respectively. Responsive to pairing, the computer can continue to collect data associated with the payment product, the vehicle that is paired with the payment product, and/or device associated with the driver that is paired with the vehicle. The collected data can be analyzed to generate reports that identify payment card fraud, driving pattern, real-time gas mileage of the vehicle, and so on. The report can also identify the paired payment card and vehicle, the paired device associated with the driver and the vehicle, and/or the paired payment card and the telematics device associated with the vehicle. The computer can present the report in a digital format and/or output the report in the form of a tangible report via an output device such as a printer.
  • Figure 1 will be discussed in the context of describing a representative operating environment associated with the automated pairing according to certain exemplary embodiments of the present invention.
  • Figure 2 will be discussed, making exemplary reference back to Figures 1 and 2 as may be appropriate or helpful.
  • Figure 3-4 will be discussed, making exemplary reference back to Figures 1 and 2 as may be appropriate or helpful.
  • the following paragraphs describe various embodiments of the method and system for automated pairing. It will be appreciated that the various embodiments discussed herein need not necessarily belong to the same group of exemplary embodiments, and may be grouped into various other embodiments not explicitly disclosed herein. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the various embodiments.
  • Figure 1 illustrates an example operating environment for automated pairing of mobile to mobile devices with other mobile to mobile devices and/or with payment products, according to certain exemplary embodiments.
  • Figure 1 illustrates a telematics server 102, a vehicle 104, a telematics device 106, a vehicle bus 108, a driver 120, a financial services card 112, a point of sale device 114, a transaction database 116.
  • the example operating environment 100 for automated paring includes a vehicle 104 equipped with a telematics device 106.
  • the telematics device 106 may be coupled to a vehicle bus 108 of the vehicle 104 and configured to collect telematics information associated with the vehicle 104 from the vehicle bus 108.
  • the telematics device 106 may be configured to timestamp the telematics information, wherein the timestamp provide information associated with a time and date at which the telematics information is obtained by the telematics device or the vehicle bus 108.
  • the telematics information may include a vehicle location data which has a timestamp.
  • the timestamp associated with the vehicle location data provides date and time at which the location of the vehicle was recorded either by the vehicle bus 108 or by the telematics device 106.
  • the telematics device 106 may transmit the collected information to the telematics server 102.
  • the telematics device 106 may be configured to transmit the telematics information of the vehicle 102 based on pre-set trigger events, i.e., the telematics device 106 may automatically transmit data when the trigger event occurs.
  • the trigger event may include, but is not limited to, turning on the ignition of the vehicle or turning off the ignition of the vehicle, reaching pre-set intervals of time or distance.
  • the telematics device 106 may be configured to transmit telematics information at regular intervals of time or distance.
  • the telematics device 106 may be configured to transmit the telematics information upon receiving a request for the telematics information associated with the vehicle 104. In yet another example embodiment, the telematics device 106 may be configured to transmit the telematics information based on a location of the vehicle. For example, when the telematics device 106 determines that the vehicle 104 has crossed a virtual geographical boundary such as geo-fence, the telematics device 106 may be configured to transmit the telematics information. In said example, the telematics device 106 may be configured to transmit telematics information when the vehicle enters a geo-fence and/or leaves the geo-fence.
  • each driver 120 may be provided with or may possess a mobile computing device 122, such as a smart phone, tablet, etc.
  • the mobile computing device 120 may have location determination capability, such as GPS capability, and the mobile computing device 122 may be configured to transmit its location to the telematics server 102 at regular intervals.
  • a client side application of the telematics server 102 may be installed in the mobile computing device 122 and may be configured to collect, time stamp, and send location information associated with the mobile computing device 122 to the telematics server 102 at regular intervals.
  • the telematics server 102 may obtain the location of the mobile computing device 122 from a service/wireless network provider associated with the mobile computing device 122.
  • each driver 120 or worker that is responsible for the vehicle 104 is provided with a financial services card 112 to cover expenses associated with the vehicle 104, such as purchasing fuel for the vehicle, maintenance of the vehicle, etc.
  • the financial services card 112 may be regulated based on certain rules such as the number of purchases that a user is allowed to make using the financial services card, specific stores and point of sale (POS) devices where the financial services card 112 may be used, the time of day that the financial services card may be used for purchases, and so on.
  • the fuel card may be void of such regulations, i.e., a driver 120 may be provided unregulated use of the financial services card 112.
  • the driver 120 may decide to use the financial services card 112 for a transaction, e.g. to refuel the vehicle 104. Accordingly, the driver 120 may use the financial services card 112 at a POS device 114 at a location of the transaction.
  • the POS device 114 may be a computing device adapted to read, authorize, and/or process the financial services card 112, e.g., a financial services card reader integrated with a cash register or a mobile card reader like Square®.
  • the financial services card 112 may be pre-authorized for purchase.
  • the driver 120 may have to enter a personal identification number (PIN) associated with the financial services card 112 which may then be validated to authorize the usage of the financial services card 112.
  • PIN personal identification number
  • the POS device 114 may be configured to transmit the card transaction data associated with the completed transaction to the transaction database 116.
  • the POS device 114 may be configured to time stamp the card transaction data, where the time stamp represents an approximate time of transaction or usage of the financial services card 112.
  • the POS device 114 may be configured to transmit the card transaction data directly to the fuel card server 118 instead of the transaction database 116.
  • the card transaction data may be transmitted in the form of batch data at a later time after the transaction using the financial services card 112 is completed, for example at the end of day or after several days.
  • the card transaction data is transmitted to the transaction database 116 at a time frame that is contemporaneous with the time of transaction.
  • the transaction database 116 as illustrated in Figure 1 comprises records identifying transaction information, such as card transaction data, for transactions completed with a financial services card 112.
  • the transaction database 116 may include, but is not limited to, an account identifier that is associated with each transaction record for that account.
  • An identification hierarchy for a transaction database record includes an account identifier, card identifier and each matching event or action. Each matching action is associated with a unique account. If a driver for a particular vehicle is assigned a unique PIN for use in connection with a transaction, the matching event or action can be associated with both the vehicle 104 and the vehicle's particular driver 120.
  • the transaction database 116 may be associated with the financial services institution, such as a bank associated with the financial services card 112.
  • the transaction database 116 may be associated with and maintained by the same entity that is associated with the telematics server 102 or another third party entity.
  • the transaction database 116 may be communicatively coupled to the telematics server 102, typically via a wired or wireless network, for collecting and processing card transaction data that is maintained by the transaction database 116.
  • the telematics server 102 includes vehicle history records comprising location data for monitored vehicles over a period of time.
  • the telematics server 102 can compare vehicle history records to card transaction data to identify data having identical or similar date/time stamps and vehicle/transaction locations. In this manner, the telematics server 102 can link or pair a specific vehicle to a particular transaction for a transaction account and the financial services card associated with the transaction, based on a substantial match of vehicle information with transaction information.
  • the telematics server 102 can link or pair a monitored mobile computing device with a specific vehicle based on a substantial match of mobile computing device location information with vehicle information. As described above, if the phone number or another unique identifier associated with the mobile computing device can be linked to a driver, then the driver can be paired with the specific vehicle.
  • the telematics server 102 is described below in greater detail in association with Figure 2.
  • Figure 2 illustrates an example functional block diagram of the telematics server illustrated in Figure 1, according to certain exemplary embodiments.
  • Figure 2 illustrates an input engine 202, a user interface engine 204, a comparison engine 206, an association engine 208, an analysis engine 210, an output engine 212, a memory 220, a processor 222, and a telematics repository 214.
  • the telematics server 102 may be implemented using one or more data processing devices. Further, the telematics server 102 may be implemented as a distributed server system where the operations of the telematics server 102 may be distributed between one or more data processors and/or a centralized server system where the operations of the telematics server 102 may be handled by a single data processor.
  • the telematics server 102 may include a processor 222.
  • the processor 222 may be a multi-core processor. In another embodiment, the processor 222 may be a combination of multiple single core processors.
  • the telematics server 102 can include a memory 220 coupled to the processor 222.
  • the memory 220 may be non-transitory storage medium, in one embodiment, and a transitory medium in another embodiment.
  • the memory 220 can include instructions that may be executed by the processor 222 to perform operations of the telematics server 102. In other words, operations associated with the different engines of the telematics server 102 may be executed using the processor 222.
  • the telematics server 102 includes a user-interface engine 204.
  • the user-interface engine 204 of the telematics server 102 may be configured to provide a web portal (e.g., web interface, hereinafter 'web interface') through which a user may access the telematics server 102.
  • a web portal e.g., web interface, hereinafter 'web interface'
  • the users can interact with the telematics server 102 using the web interface provided by the user interface engine 216.
  • the user-interface engine 204 may be configured to authenticate the users prior to providing access to the telematics server 102.
  • the users authenticated to access the telematics server 102 through the web portal may include, but are not limited to, a server administrator, driver 120, authorized entities such as vehicle fleet management companies, and/or application developers.
  • the data stored in the telematics server 102 may be accessed using an API associated with the telematics server 102.
  • application developers may access the data stored in the telematics server 102 using the API to develop applications based on the data stored in the telematics server 102.
  • the user-interface engine 204 may be configured to display information available in the vehicle information repository 214 through the web interface.
  • Authorized users may be allowed to browse the data stored in the various repositories of the telematics server 102 and further run analytics as permitted.
  • an administrator may have permission for editing and for maintenance of the various engines of the telematics server 102 and their operations.
  • the telematics server 102 also includes an input engine 202 and output engine 212 configured to enable communication to and from the telematics server 102.
  • the input engine 202 may be configured to receive telematics information from the telematics device 106 associated with the vehicle 104.
  • the input engine 202 stores the received telematics information as vehicle history records in the telematics repository 214.
  • a typical vehicle history record includes, but is not limited to, VIN, vehicle locations in GPS coordinates, date and time for the vehicle location.
  • vehicles with a GPS receiver and a telematics device 106 can send vehicle information, such as location information, to the telematics server 102 on a periodic basis or in response to a trigger event (such as starting or stopping the vehicle's engine or crossing a geo-fence).
  • vehicle information such as location information
  • a vehicle history record may also include 'direct' vehicle measurements, such as oil temperature or engine temperature or seat belt engagement that are collected directly by the vehicle's processors (vehicle bus 108) and communicated to a central collection site such as the telematics server 102.
  • the vehicle history records may also include 'indirect' measurements that are calculated by the analytics engine 210 of the telematics server 102 using various permutations of direct measurements.
  • An exemplary indirect measurement is represented by a virtual odometer, where total mileage of a vehicle can be calculated over time (odometer) by accumulating readings of latitude /longitude coordinates for location data over time - essentially space-time information for the vehicle.
  • the input engine 202 may be configured to receive inputs from one or more mobile computing device, e.g., mobile computing device 122, and the transactions database 116.
  • the input received by the input engine 202 may include, but is not limited to, location information associated with each monitored mobile computing device 122 and card transaction data associated with transactions made using each monitored financial services card 112.
  • the card transaction data can be received as and when a financial services card 112 is used for transaction and/or at a later time in the form of batch data.
  • the card transaction data can include, but is not limited to, location information associated with the transaction and other transaction details, such as card identifier number, purchased items, amount of purchase, and so on.
  • location information may include at least a location and a time stamp associated with the location.
  • the telematics server 102 may be configured to send requests through the output engine 212 for receiving location information.
  • the input engine 202 is configured to communicate the received location information with the comparison engine 206.
  • the comparison engine 206 accesses the telematics repository 214 to retrieve vehicle history records.
  • the retrieved vehicle history records are compared against the received location information associated with mobile computing device and/or the transaction to find a unique match.
  • the comparison engine 206 compares the location and date/time information to determine whether any vehicles associated with the vehicle history record were located at the transaction (point of sale) location at the transaction date and time. If the location of only one vehicle matches the transaction location and date/time information, then the comparison engine 206 communicates with the association engine 208 to associate or pair the financial services card associated with the transaction and the matched vehicle.
  • a successful match represents a matching or linking of location and date/time stamp data for a transaction with a vehicle location for a date and time.
  • the successful match links or pairs a specific vehicle with a particular transaction and the financial services card 112 associated with the transaction.
  • the comparison engine 206 compares the location and date/time information to determine whether any vehicles associated with the vehicle history record were located at the location of the mobile computing device 122 at the date and time associated with the location of the mobile computing device 122. Upon identifying a successful match, the comparison engine 206 communicates with the association engine 208 to associate or pair the mobile computing device and the matched vehicle. Further, the association engine 208 determines if the mobile computing device 122 is linked to a user, e.g., driver 120. If the mobile computing device 122 is linked to a driver 120, the association engine 208 pairs the driver 120 with the matched vehicle 104.
  • Each association may be stored in the telematics repository 214 by the association engine 208.
  • the comparison engine 206 can re -run the comparison task in response to receipt of card transaction data associated with subsequent transactions and/or a mobile computing device location at a subsequent time.
  • the comparison engine 206 can use the card transaction data associated with subsequent transactions made using the financial service card 112 and/or a mobile computing device location at a subsequent time to further reinforce the match or update the match.
  • a range or percentage location data and date/time data may be established for identifying a substantial match arising from comparison of transaction data and/or mobile computing device location data to the vehicle history records.
  • a substantial match can be identified by either a perfect one-to-one data comparison - identical location and date/time information - or location or date/time data sets that are within a pre-determined value range to represent a match.
  • a representative threshold for a match of location date is established by a radius of 0.1 or 0.2 miles around the location for a specific retail or services outlet, such as a fueling station.
  • FIG. 3-4 the operations of the telematics server 102 are described in greater detail below in association with Figures 3-4. Accordingly, turning now to Figures 3-4, these figures include flow charts that illustrate the process of automated pairing of a vehicle to a payment product and/or a mobile computing device and its corresponding user. Although specific operations are disclosed in the flowcharts illustrated in Figures 3-4, such operations are exemplary. That is, embodiments of the present invention are well suited to performing various other operations or variations of the operations recited in the flowcharts. It is appreciated that the operations in the flowcharts illustrated in Figures 3- 4 may be performed in an order different than presented, and that not all of the operations in the flowcharts may be performed.
  • this figure is a flow chart that illustrates a process of automated pairing of mobile to mobile devices (telematics device) with payment products, according to certain exemplary embodiments.
  • the input engine 202 of the telematics server 102 receives and stores telematics information associated with one or more monitored vehicles 104 that are equipped with the telematics device 106.
  • the telematics device 106 of each vehicle 104 may be configured to collect and transmit the telematics information associated with the respective vehicle 104 to the telematics server 102 in response to a trigger event (such as starting or stopping the vehicle's engine or crossing a geo-fence).
  • a trigger event such as starting or stopping the vehicle's engine or crossing a geo-fence
  • the telematics information includes at least a location of the monitored vehicle 104 and a time stamp associated with the location of the monitored vehicle 104. For example, if the location of the vehicle is recorded or obtained by the telematics device 106 at 4: 10 pm on October 1, 2009, then, the time stamp associated with the location of the vehicle will indicate the time as 4: 10 pm and date as October 1, 2009.
  • the input engine 202 of the telematics server 102 receives card transaction data associated with a transaction made using the financial services card 112.
  • a swipe of the financial services card 112 at a PoS device 114 results in the creation of card transaction data in the form of a transaction payment record that includes transaction data, such as account identifier and/or card identifier, purchase amount, identification of purchased goods or services (for example, the amount of purchased fuel), date and time (date and time stamp) of the transaction and the known location for the transaction (for example, the location of the PoS device 114, in latitude and longitude coordinates).
  • the card transaction data is recorded in the transaction database 116 as transaction payment records which is then forwarded to the telematics server 102 either automatically or upon request from the telematics server 102.
  • the comparison engine 206 of the telematics server 102 Upon receiving the card transaction data, in operations 306 and 308, the comparison engine 206 of the telematics server 102 compares the card transaction data and the telematics information to identify a substantial match between the location of the transaction obtained from the card transaction data and the location of the vehicle 104 obtained from the telematics information at a time and date of the transaction associated with the card transaction data. If a substantial match is determined, in operation 310, the comparison engine 206 further checks if the transaction location associated with the card transaction data matches the location of more than one monitored vehicle.
  • the telematics server 102 waits to receive card transaction data associated with a subsequent transaction. Once card transaction data associated with a subsequent transaction is received, in operation 316, the telematics server 102 checks to determine if a pre-determined number 'n' of comparisons have been completed. The pre-determined number 'n' can be user-set. In operation 316, if the pre-determined number of comparisons has not been reached, the telematics server 102 returns to operation 306 to re-run the comparison based on card transaction data associated with the subsequent transaction and the telematics information to identify a unique match.
  • operation 316 if the pre-determined number of comparisons has been reached, the process ends.
  • the condition provided in operation 316 can be adapted such that the telematics server 102 re-runs the comparisons till a one-to-many match has been reduced to a one-to-one match between the transaction and the vehicle.
  • the association engine 208 is configured to pair the transaction with the matched vehicle. Further, the financial services card associated with the transaction is paired with the matched vehicle. In some embodiments, if the financial services card 112 can be traced back to the driver 120, the association engine 208 can pair the driver 120 to the vehicle 104. Each pairing is then recorded in the telematics repository 214 to assist with additional analytics, such as to determine driving patterns, driver characteristics, fueling pattern of the vehicle for each driver, real-time mileage of the vehicle, etc.
  • FIG 4 is a flow chart that illustrates a process of automated pairing of mobile to mobile devices (telematics device) with other mobile to mobile devices (mobile computing device 122 of driver 120), according to certain exemplary embodiments.
  • the input engine 202 of the telematics server 102 receives and stores telematics information associated with one or more monitored vehicles 104 that are equipped with the telematics device 106.
  • the input engine 202 of the telematics server 102 receives device data associated with a monitored mobile computing device 122.
  • the device data includes at least a location associated with the mobile computing device 122.
  • the device data also includes, but is not limited to, user associated with the mobile computing device 122, unique identifier associated with the mobile computing device 122, such as phone number, physical address, and so on.
  • the mobile computing device 122 may be configured to transmit the device data comprising the location of the mobile computing device 122 at regular intervals or upon receiving a request from the telematics server 102.
  • the telematics server 102 can receive the device data comprising the location of the mobile computing device 122 from external sources, such as the wireless network/service provider associated with the mobile computing device 122.
  • the comparison engine 206 of the telematics server 102 Upon receiving the device data comprising the location of the mobile computing device 122, in operations 406 and 408, the comparison engine 206 of the telematics server 102 compares the device data and the telematics information to identify a substantial match between the location of the mobile computing device 122 obtained from the device data and the location of the vehicle 104 obtained from the telematics information at a time and date associated with the location of the mobile computing device 122. If a substantial match is determined, in operation 410, the comparison engine 206 further checks if the mobile computing device location associated matches the location of more than one monitored vehicle.
  • the telematics server 102 waits to receive the location of the mobile computing device 122 at a subsequent time. Once the location of the mobile computing device 122 at a subsequent time is received, in operation 416, the telematics server 102 checks to determine if a pre-determined number 'n' of comparisons have been completed. In operation 416, if the pre-determined number of comparisons has not been reached, the telematics server 102 returns to operation 406 to re-run the comparison based on the location of the mobile computing device 122 at a subsequent time and the telematics information to identify a unique match.
  • operation 416 if the pre-determined number of comparisons has been reached, the process ends.
  • the condition provided in operation 416 can be adapted such that the telematics server 102 re -runs the comparisons till a one -to-many match has been reduced to a one-to-one match between the mobile computing device 122 and the vehicle 104.
  • the association engine 208 is configured to pair the mobile computing device 122 with the matched vehicle. Further, the association engine 208 can pair the matched vehicle with the driver 120 associated with the mobile computing device 122. Each pairing is then recorded in the telematics repository 214 for addition operations and analytics.
  • a fleet management company ABC has ten vehicles numbered 1 to 10 that are used for various operations associated with the company. Each vehicle is equipped with a telematics device that is configured to send telematics data to a telematics server in response to a trigger event (e.g., regular intervals, start and stop of engine, entering and leaving a geo-fence).
  • the fleet management company ABC provides a financial services card M to its employee John Doe and a financial services card N to another employee Jane Roe. Additionally, John Doe also receives a smart phone S from the company.
  • the financial services card M that is provided to John Doe may be configured to be used only for fuel purchase while financial services card N provided to Jane Roe does not have any usage restrictions.
  • John Doe may decide to use one of the ten vehicles for his business related travel on March 6, 2010. During his travel on March 6, 2010, John Doe may decide to re-fuel his vehicle using his company provided financial services card M. In particular, John
  • Doe may decide to re-fuel his vehicle at 9: 10 am on the day of his travel, i.e., March 6, 2010 in a gas station at location X.
  • the POS device 114 where John Doe uses the financial services card M creates card transaction data associated with the financial services card M and records it in the transaction database 116.
  • the card transaction data identifies at least the usage of the financial services card M at location X at 9: 10 am on March 6, 2010.
  • the transaction database 116 communicates with the telematics server 102 to notify the reception of a card transaction data associated with a financial services card M.
  • the telematics server 102 may have defined rules of engagement with the transaction database 116 ahead of time.
  • the rules of engagement may state that the transaction database 116 is to notify the telematics server 102 regarding any activity associated with financial services cards M and N. Accordingly, upon receiving a card transaction data associated with financial services card M, the transaction database 116 notifies and forwards the card transaction data to the telematics server 102.
  • the telematics server 102 retrieves the time, date, and location of the transaction from the card transaction data. Then, the telematics server 102 compares the location of the transaction with the location of each of the ten vehicles obtained from their respective telematics data stored in the telematics repository of the telematics server 102.
  • the comparison determines if the location of the transaction substantially matches the location of at least one of the ten vehicles at the time and date of the transaction. That is, the telematics server 102 determines if any of the ten vehicles were present at location X or within a threshold distance of location X at 9: 10 am on March 6, 2010. In said example, the result of the comparison may output vehicle 5 as being present at location X at 9:10 am on March 6, 2010. Accordingly, the telematics server 102 associates or links the financial services card M and the vehicle 5. The pairing may then be stored in a table within a database/repository of the telematics server 102.
  • the telematics server 102 may also receive device information including at least a location of the smart phone S. Further, the telematics server 102 may compare the location of the smart phone S with the location of the ten vehicles obtained from their respective telematics data stored in the telematics repository 214. In said example, the location of the smart phone S may be location X at 9: 10 am on March 6, 2010, provided John Doe had the phone with him when he was at the gas station for refueling vehicle 5. Accordingly, the telematics server 102 may check if any of the ten vehicles were at location X of the smart phone S at 9: 10 am on March 6, 2010.
  • the telematics server 102 may determine that vehicle 5 was at location X at 9: 10 am on March 6, 2010. Accordingly, the telematics server 102 associates or links the smart phone S and the vehicle 5. If the smart phone S can be traced back to John Doe, the telematics server 102 further associates or links John Doe to vehicle 5. Accordingly, the fleet management company ABC need not associate a user and/or a financial services card to a vehicle ahead of time. Instead, the associations can be automatically made on the go.
  • the transaction location based comparison and the smart phone location based comparison may occur one after the other.
  • the transaction location based comparison and the smart phone location based comparison can be combined to form a single comparison condition.
  • Jane Roe decides to use one of the ten vehicles for her business related travel. Jane Roe may decide to follow John Doe because Jane Roe is not familiar with the route. When John Doe pulls into the gas station at location X, John Roe does the same, but does not re-fuel her vehicle.
  • the telematics server 102 upon comparison of the location of transaction with the location of the ten vehicles at the time and date of transaction, the telematics server 102 will identify both vehicle 5 and vehicle 8 as being present at location X at 9:10 am on March 6, 2010. In this situation, the telematics server 102 waits for the next card transaction data associated with a subsequent transaction using the financial service card M.
  • the telematics server 102 will converge on match between vehicle 5 and the financial services card M and eliminate the match between vehicle 8 of Jane Roe and the financial services card M.
  • the telematics server 102 can re -run the comparisons using transaction location associated with previous transactions, i.e., historical transactions instead of waiting for card transaction data associated with subsequent transactions.
  • each pairing can be reinforced by re-running the comparisons for a pre-determined number of times.
  • the various devices and modules described herein may be enabled and operated using hardware circuitry (e.g., CMOS based logic circuitry), firmware, software or any combination of hardware, firmware, and software (e.g., embodied in a machine readable medium).
  • hardware circuitry e.g., CMOS based logic circuitry
  • firmware e.g., software or any combination of hardware, firmware, and software (e.g., embodied in a machine readable medium).
  • the various electrical structures and methods may be embodied using transistors, logic gates, and electrical circuits (e.g., application specific integrated (ASIC) circuitry and/or in Digital Signal Processor (DSP) circuitry).
  • ASIC application specific integrated
  • DSP Digital Signal Processor
  • invention intend to refer broadly to all disclosed subject matter and teaching, and recitations containing these terms should not be misconstrued as limiting the subject matter taught herein or to limit the meaning or scope of the claims. From the description of the exemplary embodiments, equivalents of the elements shown therein will suggest themselves to those skilled in the art, and ways of constructing other embodiments of the present invention will appear to practitioners of the art. Therefore, the scope of the present invention is to be limited only by the claims that follow.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computing Systems (AREA)
  • Traffic Control Systems (AREA)

Abstract

L'invention fait notamment intervenir un ordinateur qui reçoit des données de transaction par carte en réaction à l'utilisation d'une carte de services financiers par une transaction. Les données de transaction par carte identifient au moins un lieu, une date et une heure associés à la transaction. Suite à la réception des données de transaction par carte, l'ordinateur compare les données de transaction par carte à des informations télématiques associées à un véhicule équipé d'un dispositif télématique. Les informations télématiques identifient au moins une position du véhicule, ainsi qu'une heure et une date associées à la position du véhicule. En se basant sur la comparaison, l'ordinateur détermine si le lieu de la transaction coïncide sensiblement avec la position du véhicule à l'heure et à la date de la transaction. En réaction à la détermination d'une coïncidence substantielle, l'ordinateur associe la carte de services financiers au véhicule.
PCT/US2014/056974 2013-09-24 2014-09-23 Appariement automatisé de produits de paiement et dispositifs de mobile à mobile WO2015048015A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201361881462P 2013-09-24 2013-09-24
US61/881,462 2013-09-24
US14/054,279 2013-10-15
US14/054,279 US9563893B2 (en) 2012-10-16 2013-10-15 Method and system for detection of a fuel card usage exception

Publications (1)

Publication Number Publication Date
WO2015048015A1 true WO2015048015A1 (fr) 2015-04-02

Family

ID=52744389

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/056974 WO2015048015A1 (fr) 2013-09-24 2014-09-23 Appariement automatisé de produits de paiement et dispositifs de mobile à mobile

Country Status (1)

Country Link
WO (1) WO2015048015A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111507718A (zh) * 2020-04-20 2020-08-07 车主邦（北京）科技有限公司 无感支付系统
CN111507700A (zh) * 2020-04-20 2020-08-07 车主邦（北京）科技有限公司 车辆支付电子标签识别方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070173993A1 (en) * 2006-01-23 2007-07-26 Nielsen Benjamin J Method and system for monitoring fleet metrics
US7406321B2 (en) * 2003-03-27 2008-07-29 General Motors Corporation Method and system for providing user-selected telematic services
US20090280771A1 (en) * 2006-07-21 2009-11-12 Telefonaktiebolaget Lm Ericsson (Publ) Emergency call system using specific mobile user information
US20100235891A1 (en) * 2009-03-13 2010-09-16 Oglesbee Robert J Method and system for facilitating synchronizing media content between a vehicle device and a user device
US20110238300A1 (en) * 2010-03-23 2011-09-29 United Parcel Service Of America, Inc. Geofence-based triggers for automated data collection
US8527135B2 (en) * 2000-07-25 2013-09-03 Hti Ip, L.L.C. Peripheral access devices and sensors for use with vehicle telematics devices and systems

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8527135B2 (en) * 2000-07-25 2013-09-03 Hti Ip, L.L.C. Peripheral access devices and sensors for use with vehicle telematics devices and systems
US7406321B2 (en) * 2003-03-27 2008-07-29 General Motors Corporation Method and system for providing user-selected telematic services
US20070173993A1 (en) * 2006-01-23 2007-07-26 Nielsen Benjamin J Method and system for monitoring fleet metrics
US20090280771A1 (en) * 2006-07-21 2009-11-12 Telefonaktiebolaget Lm Ericsson (Publ) Emergency call system using specific mobile user information
US20100235891A1 (en) * 2009-03-13 2010-09-16 Oglesbee Robert J Method and system for facilitating synchronizing media content between a vehicle device and a user device
US20110238300A1 (en) * 2010-03-23 2011-09-29 United Parcel Service Of America, Inc. Geofence-based triggers for automated data collection

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111507718A (zh) * 2020-04-20 2020-08-07 车主邦（北京）科技有限公司 无感支付系统
CN111507700A (zh) * 2020-04-20 2020-08-07 车主邦（北京）科技有限公司 车辆支付电子标签识别方法
CN111507718B (zh) * 2020-04-20 2023-09-01 车主邦（北京）科技有限公司 无感支付系统
CN111507700B (zh) * 2020-04-20 2023-12-05 车主邦（北京）科技有限公司 车辆支付电子标签识别方法

Similar Documents

Publication Publication Date Title
US9940615B2 (en) Automated pairing of payment products and mobile to mobile devices
US9576291B2 (en) Method and system for detection of a fuel card usage exception
US11301936B1 (en) Using a distributed ledger for total loss management
US10580001B2 (en) Vehicle transaction data communication using communication device
US9412108B2 (en) Systems and methods for fraud detection by transaction ticket size pattern
US9552578B2 (en) Method and system for authentication of payment card transactions
US20100191674A1 (en) Method and System for Assessment, Collection, and Disbursement of Funds Related to Motor Vehicles
US20100332363A1 (en) Payment cards and fuel cards
KR20180090866A (ko) 지불 거래와 관련하여 차량 연결성을 이용한 시스템 및 방법
US20160267451A1 (en) Payment processing based on vehicle remote identification
WO2015002833A1 (fr) Systèmes et procédés destinés à un service de prise de décision basée sur le risque, ledit service intégrant des transactions par carte de paiement et des événements d'application
US20160125400A1 (en) Systems and methods for geo component fraud detection for card-present transactions
US20180144322A1 (en) Systems and methods for validating a transaction based on vehicle location
US20160132857A1 (en) Systems and methods for determining an actual geograhpic location of a payment transaction
US20160239853A1 (en) Method and system for providing insights to merchants based on consumer transaction history
US11961085B2 (en) Systems and methods for setting spend limits and counteracting fraud in gas station transaction
WO2015048015A1 (fr) Appariement automatisé de produits de paiement et dispositifs de mobile à mobile
US20150058187A1 (en) Mileage Tax Estimation Using Payment Network Data
US20200013030A1 (en) Systems and Methods for Fraud Reduction
US20140172690A1 (en) Systems and Methods For Matching Domain Specific Transactions
US20180121971A1 (en) Method and system for parking rate estimation based on geolocation and payment history
US20140236822A1 (en) System and method for vehicular fleet management
WO2016200573A1 (fr) Systèmes et procédés destinés à être utilisés dans le traitement de transactions au niveau de comptes de paiement
JP7390538B2 (ja) センターバリュー型バス運賃決済システム
US20170083958A1 (en) Method and system for assessing parking capacity

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 14849998

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 14849998

Country of ref document: EP

Kind code of ref document: A1