Method and system for correlating mobile device location with electronic transaction data

Abstract

A method for privacy protection in use of geolocation for transaction authorization includes: storing location profiles including a device identifier and account identifier; receiving a location notification including a specific device identifier and a geolocation; identifying a specific location profile including the specific device identifier; transmitting the geolocation and the account identifier in the specific location profile to a second computing device; receiving, at the second computing device, a transaction message related to a payment transaction including an account number corresponding to the account identifier, a transaction location, and authorization data; determining if the geolocation corresponds to the transaction location; storing a result of the determination in the authorization data; and transmitting the transaction message to a financial institution associated with a transaction account corresponding to the account number.

What is claimed is: 
     
         1 . A method for privacy protection in use of geolocation for transaction authorization, comprising:
 storing, in a location database of a first computing device, a plurality of location profiles, wherein each location profile includes a structured data set related to a mobile computing device, the location profile including at least a device identifier and an account identifier;   receiving, by a receiving device of the first computing device, a location notification from a third party system, the location notification including at least a specific device identifier and a geolocation;   executing, by a querying module of the first computing device, a query on the location database to identify a specific location profile where the included device identifier corresponds to the specific device identifier;   electronically transmitting, by a transmitting device of the first computing device, at least the geolocation and the account identifier included in the identified specific location profile to a second computing device;   receiving, by a receiving device of the second computing device, a transaction message related to a payment transaction via a payment network, wherein the transaction message is formatted pursuant to one or more standards and includes at least a plurality of data elements including at least a first data element configured to store a primary account number corresponding to the account identifier transmitted to the second computing device, a second data element configured to store a transaction location, a third data element configured to store authorization data, and one or more additional data elements configured to store additional transaction data;   determining, by a transaction processing module of the second computing device, if the geolocation transmitted to the second computing device corresponds to the transaction location stored in the second data element included in the received transaction message;   storing, by the transaction processing module of the second computing device, a result of the determination in the third data element included in the received transaction message; and   electronically transmitting, by a transmitting device of the second computing device, the transaction message including the third data element storing the result of the determination to a financial institution associated with a transaction account corresponding to the primary account number stored in the first data element included in the transaction message via the payment network.   
     
     
         2 . The method of  claim 1 , further comprising:
 generating, by a hashing module of the second computing device, a hash value via application of one or more hashing algorithms to the primary account number stored in the first data element included in the received transaction message, wherein   the generated hash value is equivalent to the account identifier transmitted to the second computing device.   
     
     
         3 . The method of  claim 1 , further comprising:
 storing, in an account database of the second computing device, a plurality of account profiles, wherein each account profile includes a structured data set related to a transaction account including at least a primary account number and an associated account identifier; and   executing, by a querying module of the second computing device, a query on the account database to identify a specific account profile where the included primary account number corresponds to the primary account number stored in the first data element included in the received transaction message, wherein   the account identifier transmitted to the second computing device corresponds to the associated account identifier included in the identified specific account profile.   
     
     
         4 . The method of  claim 1 , further comprising:
 generating, by a hashing module of the first computing device, a hash value via application of one or more hashing algorithms to the specific device identifier included in the received location notification, wherein   the generated hash value is equivalent to the device identifier included in the identified specific location profile.   
     
     
         5 . The method of  claim 1 , further comprising:
 executing, by the querying module of the first computing device, a second query on the location database to store the geolocation included in the received location notification in the identified specific location profile.   
     
     
         6 . The method of  claim 1 , further comprising:
 receiving, by the receiving device of the second computing device, at least the geolocation and the account identifier included in the identified specific location profile transmitted by the transmitting device of the first computing device.   
     
     
         7 . The method of  claim 1 , wherein the first computing device does not possess or receive the primary account number stored in the first data element included in the received transaction message. 
     
     
         8 . The method of  claim 1 , wherein the second computing device does not possess or receive the specific device identifier included in the received notification location. 
     
     
         9 . The method of  claim 1 , wherein each account identifier is hash value generated via application of a hashing algorithm to an account number corresponding to a related transaction account. 
     
     
         10 . The method of  claim 1 , wherein the transaction message further includes a message type indicator indicative of an authorization request. 
     
     
         11 . A system for privacy protection in use of geolocation for transaction authorization, comprising:
 a location database of a first computing device configured to store a plurality of location profiles, wherein each location profile includes a structured data set related to a mobile computing device, the location profile including at least a device identifier and an account identifier;   a receiving device of the first computing device configured to receive a location notification from a third party system, the location notification including at least a specific device identifier and a geolocation;   a querying module of the first computing device configured to execute a query on the location database to identify a specific location profile where the included device identifier corresponds to the specific device identifier;   a transmitting device of the first computing device configured to electronically transmit at least the geolocation and the account identifier included in the identified specific location profile to a second computing device;   a receiving device of the second computing device configured to receive a transaction message related to a payment transaction via a payment network, wherein the transaction message is formatted pursuant to one or more standards and includes at least a plurality of data elements including at least a first data element configured to store a primary account number corresponding to the account identifier transmitted to the second computing device, a second data element configured to store a transaction location, a third data element configured to store authorization data, and one or more additional data elements configured to store additional transaction data;   a transaction processing module of the second computing device configured to
 determine if the geolocation transmitted to the second computing device corresponds to the transaction location stored in the second data element included in the received transaction message, and 
 store a result of the determination in the third data element included in the received transaction message; and 
   a transmitting device of the second computing device configured to electronically transmit the transaction message including the third data element storing the result of the determination to a financial institution associated with a transaction account corresponding to the primary account number stored in the first data element included in the transaction message via the payment network.   
     
     
         12 . The system of  claim 11 , further comprising:
 a hashing module of the second computing device configured to generate a hash value via application of one or more hashing algorithms to the primary account number stored in the first data element included in the received transaction message, wherein   the generated hash value is equivalent to the account identifier transmitted to the second computing device.   
     
     
         13 . The system of  claim 11 , further comprising:
 an account database of the second computing device configured to store a plurality of account profiles, wherein each account profile includes a structured data set related to a transaction account including at least a primary account number and an associated account identifier; and   a querying module of the second computing device configured to execute a query on the account database to identify a specific account profile where the included primary account number corresponds to the primary account number stored in the first data element included in the received transaction message, wherein   the account identifier transmitted to the second computing device corresponds to the associated account identifier included in the identified specific account profile.   
     
     
         14 . The system of  claim 11 , further comprising:
 a hashing module of the first computing device configured to generate a hash value via application of one or more hashing algorithms to the specific device identifier included in the received location notification, wherein   the generated hash value is equivalent to the device identifier included in the identified specific location profile.   
     
     
         15 . The system of  claim 11 , wherein the querying module of the first computing device is further configured to execute a second query on the location database to store the geolocation included in the received location notification in the identified specific location profile. 
     
     
         16 . The system of  claim 11 , wherein the receiving device of the second computing device is further configured to receive at least the geolocation and the account identifier included in the identified specific location profile transmitted by the transmitting device of the first computing device. 
     
     
         17 . The system of  claim 11 , wherein the first computing device does not possess or receive the primary account number stored in the first data element included in the received transaction message. 
     
     
         18 . The system of  claim 11 , wherein the second computing device does not possess or receive the specific device identifier included in the received notification location. 
     
     
         19 . The system of  claim 11 , wherein each account identifier is hash value generated via application of a hashing algorithm to an account number corresponding to a related transaction account. 
     
     
         20 . The system of  claim 11 , wherein the transaction message further includes a message type indicator indicative of an authorization request.