Systems and methods for collecting device data from digital wallet authentication

Abstract

The present invention relates to systems and methods for collecting device data from digital wallet authentication. A computer-based method for collecting digital wallet data from a digital wallet transaction initiated by a user is provided. The method includes receiving registration data of the user in response to the user registering to a digital wallet application, wherein the registration data includes demographic data and device registration data including a device identifier for identifying the user device when the user device communicates with another computing device. The method further includes storing the registration data in at least one memory device, and receiving digital wallet data as part of a digital wallet transaction initiated by the user using the digital wallet application on the user device, wherein the digital wallet data includes transaction data, device communication data, and biometric data. The method further includes comparing the digital wallet data to the registration data, and linking the digital wallet data in the at least one memory device to the registration data.

Description

[0001] This application is a divisional application of the PCT application filed on December 1, 2017, with national application number 201780084108.5 and entitled "System and method for collecting device data from digital wallet authentication", which has entered the Chinese national phase.

[0002] Cross-references to related applications

[0003] This application claims the benefit and priority of U.S. Patent Application 15 / 410,466, filed January 19, 2017. The entire disclosure of the above application is incorporated herein by reference. Technical Field

[0004] This disclosure generally relates to collecting device data from computing devices used in digital wallet transactions, and more specifically, to systems and methods for determining user demographics by using device communication data and biometric data collected from user computing devices capable of accessing digital wallet applications. Background Technology

[0005] Consumers can often use a variety of methods to make payment transactions to purchase goods and services. These methods include using cash, plastic payment cards, smartphones, and other user-operated computing devices (also known as user computing devices) that provide account and transaction data to complete the purchase. In cases where account data is transmitted for a transaction, the payment processor computing device processes the payment transaction via a processing network. The payment card and / or user computing device can (in this context, referred to as a merchant location transaction) be used at a merchant-operated point-of-sale (POS) device, or the user can initiate the transaction without being physically located at the merchant's location (e.g., an online transaction initiated from home, such as ordering goods from a merchant's website). The latter type of transaction is sometimes also referred to as a card-not-present (CNP) transaction because the payment card is not physically presented at the merchant's location. In some cases, merchant location transactions and CNP transactions can be performed using a digital wallet, which is stored as an application on the user's smartphone or as an account archive on another user computing device.

[0006] Digital wallets are typically applications accessed by users from computing devices. A computing device can be a device associated with the user, such as a smartphone, tablet, or wearable computing device. A computing device can also be a laptop, desktop computer, or other electronic device. Digital wallet applications allow users to purchase items using their computing devices without using physical cards. For example, a user might want to buy coffee. Instead of retrieving a physical card from a physical wallet, the user can activate their digital wallet application on their computing device and use the card data associated with the digital wallet to purchase the coffee. In another example, a user might want to buy something from a website, such as concert tickets. Instead of entering their account information on the website to complete the transaction, the user can access their digital wallet application on their computing device and use the card data associated with the digital wallet to purchase the tickets. Typically, digital wallets require biometric authentication from the user to complete the purchase. Biometric authentication is the processing of biometric data that verifies the user's identity by measuring the user's unique characteristics. Biometric data can include passwords, fingerprints, facial recognition, voice recognition, and / or any other biometric data used for verification. In one instance, the biometric authentication process may occur at the user's computing device. In another instance, biometric authentication processing can occur at another computing device.

[0007] When a digital wallet transaction is executed, certain device communication data (also known as metadata) is generated by the user's device. In some cases, this metadata can be accessed by the merchant's computing device (e.g., a website) or POS device during the purchase. A system is needed that can capture this metadata along with biometric data and combine it with transaction data. By doing so, certain outputs can be generated for various users. Having a system capable of capturing this data and generating such outputs would be beneficial. Summary of the Invention

[0008] In one aspect, a computer-based method is provided for collecting digital wallet data from user-initiated digital wallet transactions to determine the user's demographics. The method is implemented using a data collector (DC) computing device including at least one processor communicating with at least one memory device. The method includes receiving user registration data in response to a user registering with a digital wallet application, wherein the registration data includes the user's demographic data and device registration data, the device registration data including a device identifier for identifying the user device when it communicates with another computing device. The method also includes storing the registration data within at least one memory device and receiving digital wallet data as part of a digital wallet transaction initiated by the user using a digital wallet application on the user's device, wherein the digital wallet data includes transaction data, device communication data, and biometric data. The method further includes comparing the digital wallet data with the registration data, linking the digital wallet data within the at least one memory device to the registration data including the user's demographic data, and determining demographic data associated with multiple users for at least one merchant.

[0009] On the other hand, a data collector (DC) computing device is provided, comprising at least one processor communicating with at least one memory device. The DC computing device is configured to receive user registration data in response to a user registering with a digital wallet application, wherein the registration data includes the user's demographic data and device registration data, the device registration data including a device identifier for identifying the user device when the user device communicates with another computing device. The DC computing device is also configured to store the registration data within the at least one memory device and to receive digital wallet data as part of a digital wallet transaction initiated by the user using a digital wallet application on the user device, wherein the digital wallet data includes transaction data, device communication data, and biometric data. The DC computing device is further configured to compare the digital wallet data with the registration data, link the stored digital wallet data to the registration data including the user's demographic data, and determine demographic data associated with multiple users for at least one merchant.

[0010] In another aspect, a non-transient computer-readable medium is provided, comprising executable instructions for collecting digital wallet data from user-initiated digital wallet transactions to determine the user's demographics. When executed by a data collector (DC) computing device including at least one processor communicating with at least one memory device, the computer-executable instructions cause the DC computing device to receive user registration data in response to a user registering with a digital wallet application, wherein the registration data includes the user's demographic data and device registration data, the device registration data including a device identifier for identifying the user device when it communicates with another computing device. The computer-executable instructions also cause the DC computing device to store the registration data within at least one memory device and receive digital wallet data as part of a digital wallet transaction initiated by the user using a digital wallet application on the user device, wherein the digital wallet data includes transaction data, device communication data, and biometric data. The computer-executable instructions further cause the DC computing device to compare the digital wallet data with the registration data, link the stored digital wallet data to the registration data including the user's demographic data, and determine demographic data associated with multiple users for at least one merchant. Attached Figure Description

[0011] Figures 1-7 Example embodiments of the methods and systems described herein are shown.

[0012] Figure 1 This is a schematic diagram of an example data collector (DC) platform used to collect device communication data, transaction data, and biometric data from digital wallet payment transactions, and to determine a user's demographics based on device communication, transaction, and biometric data.

[0013] Figure 2 yes Figure 1 The block diagram of the DC platform shown includes multiple example computing devices that are communicatively coupled to each other via multiple network connections.

[0014] Figure 3 The diagram includes Figure 2 The example configuration of the DC computing device or the server system communicating with the DC computing device is shown in the figure.

[0015] Figure 4 The illustration shows an example configuration of a user system, such as a user computer device configured to send user demographic data and payment card transaction location data.

[0016] Figure 5 Example configurations of server systems are shown, such as Figure 2 The DC computing device shown in the image.

[0017] Figure 6A and Figure 6B This illustration shows an example method flow of how a DC computing device collects device communication, transaction, and biometric data.

[0018] Figure 7 An example configuration of a database within a DC computing device is shown, which collects device communication, transaction, and biometric data.

[0019] The same numbers in the diagram indicate parts that are the same or have similar functions. Detailed Implementation

[0020] This disclosure relates to a data collector (DC) computing platform configured to collect device communication data and biometric data from a user computing device used to initiate payment transactions with merchants using a digital wallet application, wherein the collected device communication data and biometric data can be used to determine the user's demographics. Similarly, the DC computing platform can determine the demographics of all such users (e.g., digital wallet users) who visit a merchant. The DC computing platform can also determine the demographics of all users visiting various such merchants. In at least some implementations, the DC computing platform includes a DC computing device that communicates with a payment processor computing device. In other embodiments, the DC computing device is integrated into or is part of the payment processor computing device. The DC computing platform is configured to collect digital wallet registration data and digital wallet data. Digital wallet registration data is collected when a user first accesses the digital wallet application. In some embodiments, a user can access the digital wallet application after downloading the application to a user computing device (such as a smartphone, tablet, or wearable computing device). In other embodiments, a user can access the digital wallet application using an internet browser (e.g., Internet Explorer) on the user computing device. Digital wallet registration data includes user demographic data and device registration data that identifies the user's computing device used for registration. Digital wallet data includes device communication data or metadata from the device the user uses to make a purchase, transaction data from payment transactions initiated by the user using the digital wallet application, and biometric data of the user when authenticating themselves to their device during a purchase.

[0021] When registering or enrolling in a digital wallet application, the user's computing device creates device registration data. During the registration process, the DC computing device receives and stores the device registration data, which may include user account data, device data associated with the user's computing device, and the user's demographic data. For example, during registration, the user may be requested to provide demographic data such as their age and preferred language. Preferred language can help determine the user's country of origin, as many countries have a national language. This demographic data may be stored in memory as part of the registration data. Device registration data may include some of this demographic and / or other device data that can be shared when the digital wallet is used to execute transactions. For example, device registration data may include device ID, browser type, IP address, user location data, biometric data, preferred language, etc. In some instances, device registration data may be automatically collected from the user's computing device or from the issuing bank associated with the user's account.

[0022] Subsequently, each time a user's computing device authorizes a transaction at a point-of-sale (POS) device associated with a merchant, the POS device sends digital wallet data to the payment processor and issuing bank via the payment network. Digital wallet data may include transaction data, device communication data or metadata, and biometric data. Transaction data includes data associated with the transaction and a transaction ID. Transaction data may include, for example, biometric authorization verification, transaction amount, merchant ID, geolocation, item data describing the goods or services being purchased, and other data associated with the transaction. Metadata may include or be related to the user's demographic data. Demographic data may be collected when the digital wallet application is verified. In some instances, digital wallet data does not include any metadata. In these instances, metadata may be provided through a separate data channel and linked to the digital wallet data via the transaction ID or some other identifier, allowing the metadata to be stored along with the transaction data. Biometric data may be part of or associated with device communication data and / or transaction data. Biometric data ensures that the user makes a purchase. Biometric authentication verification is confirmation of successful biometric authentication. The DC computing device obtains transaction data, metadata, and biometric data through the user's digital wallet application.

[0023] Digital wallet data is received at the payment processor where it is processed for payment. Any metadata provided with or combined with the digital wallet data is stored in the payment processor's database. This data is then used to determine the user's demographic data (country of origin, age group, etc.). For example, demographic data may be included in the metadata, or it may be determined by performing a lookup using at least a portion of the metadata. The lookup may be performed at the payment processor's database or at the issuing bank's database, where the user's demographic data is stored as part of the digital wallet registration process.

[0024] As part of every digital wallet transaction, the user's computing device verifies the user via biometric authentication. This verifies that the user is making a purchase at a merchant (e.g., geographical location or website). Digital wallet transactions occur through a digital wallet application coupled to the computing device. Physical cards are often stolen or used remotely. User verification prevents data skew in cases of stolen cards or remote purchases. When using a digital wallet application, biometric authentication ensures that it is indeed the user making the purchase.

[0025] In some embodiments, the DC computing device receives digital wallet data from the POS device. In one example, the user's computing device can initiate a digital wallet transaction with the POS device. In doing so, digital wallet data (including transaction data and metadata) is transmitted to the POS device. Other digital wallet data (such as biometric data) used to verify the user's identity when using the digital wallet application can also be transmitted to the POS device. The POS device then sends this digital wallet data to a payment processor to process the transaction. In another example, the user can use a payment card to initiate a transaction with the POS device. The POS device then sends transaction data, including but not limited to the primary account number (PAN) including the user's bank identification number (BIN), to the payment processor to process the transaction. Subsequently, the DC computing device uses this transaction data to perform a lookup in the PAN's digital wallet registration data to determine if the user is registered in the digital wallet application. If the DC computing device determines that the user is registered in the digital wallet application, then the DC computing device collects the digital wallet data corresponding to the user. The DC computing device also tags the PAN so that future transactions initiated by the user using a payment card are automatically linked to the user's digital wallet data.

[0026] In an alternative embodiment, the DC computing device receives digital wallet data as it is transmitted between the user's computing device and the payment processor. In an example embodiment, the digital wallet data includes metadata. For example, a user can use a digital wallet application to purchase food at a restaurant in New York City. The digital wallet data containing metadata is sent to the payment processor that authorized the transaction. This metadata may include device ID, browser type, IP address, location data, biometric data, preferred language, etc. In some instances, metadata may be automatically collected from the user's computing device or an issuing bank associated with the user's account. Once the metadata is received by the payment processor, it is coupled with other data stored in the DC computing platform, which may include the stored digital wallet data.

[0027] Digital wallet data is stored in a payment processor database associated with the payment processor. Additionally, other demographic data (country of origin, age group, etc.) and biometric data associated with the user can also be stored in the same database. Therefore, the payment processor database can include data that can be used to verify a user's purchases and / or visits to a specific location, and can provide certain demographic data associated with the user.

[0028] The DC computing device is configured to receive digital wallet data for digital wallet transactions using a payment card account associated with a user. The digital wallet data may include metadata containing the user's demographics and the location where the purchase was made. The digital wallet data may also include the merchant's location and the type of goods or services purchased. For example, the DC computing device may receive digital wallet data that includes metadata providing the location of the user's computing device. The DC computing device can determine this location by receiving GPS (geolocation) coordinates from the user's computing device or by performing a lookup using a merchant identifier received along with the digital wallet data. The user's computing device geolocation can suggest the merchant's location. However, in some instances, a user may purchase goods or services on a website without needing to be physically present at the merchant's location. To accurately determine the merchant's location, the DC computing device can use transaction data to determine the merchant's registered address and / or place of business. The DC computing device can also determine the merchant's location when it receives digital wallet data from a POS device. In this case, the DC computing device may receive the POS device's IP address, which allows the DC computing device to determine the POS device's location and thus the merchant's location. DC computing devices can also receive demographic data including age, sex, and / or place of origin (e.g., the user's home address and / or preferred language).

[0029] In at least some implementations, the DC computing device is configured to compare digital wallet data with registration data. This comparison can be performed to identify a registered user associated with the received digital wallet data. In doing so, the DC computing device can compare the user's biometric data included in the digital wallet data with the user's identifier stored as part of the registration data. The DC computing device can also compare device registration data with device communication data to determine that the user computing device used to send the digital wallet data belongs to a registered user. To perform the comparison, the DC computing device can retrieve the user's registration data from a payment processor database and associate this data with the user's digital wallet data. Once the registration data is retrieved, the DC computing device compares the registration data with the digital wallet data.

[0030] Subsequently, the DC computing device links the user's corresponding digital wallet data with their registration data. More specifically, transaction data in the digital wallet data is linked to demographic data in the registration data. For example, transaction data providing information such as merchant location, purchase time, and type of service or goods purchased is coupled with registration data including the user's age and place of origin. By linking digital wallet data to registration data, the DC computing device can determine the types of demographic groups that frequently visit a merchant's location during a specific time period.

[0031] In some embodiments, the DC computing device can be used to generate business recommendations based on specific demographics (age, country of origin, etc.) of actual visitors to attractions, venues, and / or businesses in these locations. Thus, when a requester requests to visit an attraction or restaurant in a new area, the DC computing platform can (i) make recommendations to the requester that include a breakdown of the types of people who have actually visited the attraction or restaurant, and the requester can determine which site to visit, or (ii) make recommendations to the requester that match the requester's demographics with those of previous visitors to that site.

[0032] For example, a requester in the 30-35 age group from the United States could travel to Edinburgh, Scotland. When a requester requests a merchant referral, the DC computing device communicates with the payment processor database to retrieve augmented data based on the requester's geographic origin and age, and generates one or more merchant recommendations based on the retrieved data. For example, the retrieved data could indicate that Edinburgh Castle is the most visited location in Edinburgh, Scotland, for US users in the 30-35 age group.

[0033] The DC computing device sends the results (e.g., one or more recommended merchants) to the requester's computing device. Merchant recommendations can be provided to the requester via SMS text displayed on a webpage or within an application.

[0034] The DC computing device is configured to receive a merchant recommendation request from a requester, which may include the requester's demographic data and locations the requester might want to visit. Demographic data may include specific age, age range (30-35), gender, place of origin (e.g., the user's home address and / or preferred language), etc. The location may include, but is not limited to, a location or candidate locations entered by the requester. In one example, the DC computing device may receive a merchant recommendation request that includes at least one location entered by the requester, such as a geographic location or domain location (e.g., a virtual location). A geographic location may include a geographic region, such as a neighborhood, county, city, state, country, etc. A domain location may correspond to a specific website (e.g., a pharmacy chain). Two or more domain locations may be associated with a domain category (e.g., a merchant selling vitamin products). In another example, the DC computing device may receive a merchant recommendation request that includes at least one candidate location (e.g., a location near the requester's computer device). At least one candidate location may be based on the requester's computer device's GPS (geolocation) coordinates and / or the computing device's GeoIP address. In other words, the DC computing device is configured to provide the requester with demographic data of users who visit a specific merchant location and make a purchase, as well as demographic data of users who visit a merchant's website and make a purchase.

[0035] In at least some implementations, the DC computing device is configured to retrieve user-related data from the payment processor database. This data includes locations the user may have visited and user demographic information. For example, the DC computing device may retrieve information providing the user's age, gender, and / or place of origin. The DC computing device may also retrieve merchant locations to identify locations the user has visited. The DC computing device can determine the merchant's location by looking at the IP address that sent the digital wallet data, the merchant's IP address or domain, or the merchant's registered address and / or business location.

[0036] In some embodiments, the DC computing device is configured to compare merchant recommendation request data with data associated with users. The DC computing device retrieves the merchant recommendation request data and matches it with user data stored in a payment processor database. For example, the DC computing device may match the destination on the merchant recommendation request with one or more merchant locations stored in the payment processor database. Once location matching is complete, the DC computing device may compare the requester's age with the ages of users stored in the payment processor database who have already made purchases at locations matching the destination on the merchant recommendation request.

[0037] Alternatively, the DC computing device can match the requester's age with the ages of users stored in the payment processor database. The DC computing device can then compare the destination on the merchant recommendation request with locations stored in the payment processor database that have been visited by users matching the requester's age.

[0038] In other embodiments, the DC computing device can match the requester's place of origin with the place of origin of users stored in the payment processor database. Subsequently, the DC computing device can compare the destination of the merchant recommendation request with locations stored in the payment processor database that have been visited by users matching the requester's place of origin.

[0039] In another embodiment, the DC computing device can match the requester's gender with the gender of users stored in the payment processor database. Subsequently, the DC computing device can compare the destination of the merchant recommendation request with locations stored in the payment processor database that have been visited by users matching the requester's gender.

[0040] In the absence of matching data between merchant referral requests and the payment processor database, the DC computing device can access the issuing bank's database to obtain user data corresponding to their demographics and the locations where they have made purchases.

[0041] In at least some embodiments, once the matching process is complete, the DC computing device is configured to generate merchant recommendations based on the matching data identified during the matching process. The DC computing device can provide specific merchant recommendations (e.g., restaurants or multiple restaurants) and / or non-specific merchant recommendations (e.g., neighborhoods or areas). The DC computing device can also provide destination recommendations targeting a specific age (e.g., 30) and / or range (e.g., 30-35).

[0042] In another embodiment, the DC computing device is configured to send merchant recommendations to a requester via SMS text displayed on a webpage or within an application. The requester can specify the type of communication channel that the DC computing device can use. Alternatively, the DC computing device can be configured to use a default transmission type when the requester does not specify a type.

[0043] The technical problems addressed by the DC computing platform include at least one of the following: (i) the inability to generate outputs that include breakdowns based on user demographic data, and (ii) the inability to generate outputs that may suggest locations that a particular demographic group might want to visit.

[0044] The methods and systems described herein can be implemented using computer programming or engineering techniques, including computer software, firmware, hardware, or any combination or subset thereof, wherein the technical effects can be achieved by: (i) receiving user registration data in response to a user registering with a digital wallet application, wherein the registration data includes the user's demographic data and device registration data, the device registration data including a device identifier used to identify the user device when the user device communicates with another computing device; (ii) storing the registration data in memory; (iii) receiving digital wallet data as part of a digital wallet transaction initiated by the user using a digital wallet application on the user's device, the digital wallet data including transaction data, device communication data, and biometric data; (iv) comparing the digital wallet data with the registration data; (v) linking the digital wallet data in memory to the registration data including the user's demographic data; and (vi) determining demographic data associated with multiple users for at least one merchant.

[0045] The resulting technological benefits achieved by the DC computing platform include at least one of the following: (i) new and improved use of existing user demographic data and purchase locations received from user and merchant computing devices, (ii) improved merchant recommendations based on demographic data and destination location, and (iii) the ability of the requester to obtain demographic segmentation of previous visitors to the site.

[0046] As used herein, a processor can include any programmable system, including systems using microcontrollers, reduced instruction set circuitry (RISC), application-specific integrated circuits (ASICs), logic circuits, and any other circuitry or processor capable of performing the functions described herein. The examples above are merely illustrative and are therefore not intended to limit the definition and / or meaning of the term "processor" in any way.

[0047] As used herein, the terms “software” and “firmware” are interchangeable and include any computer program stored in memory for execution by a processor, including RAM memory, ROM memory, EPROM memory, EEPROM memory, and non-volatile RAM (NVRAM) memory. The memory types described above are merely examples and therefore do not limit the types of memory that can be used to store computer programs.

[0048] In one embodiment, a computer program is provided, and the program is implemented on a computer-readable storage medium. In an example embodiment, the system executes on a single computer system without needing to be connected to a server computer. In another embodiment, the system... The system runs in an environment (Windows is a registered trademark of Microsoft Corporation, Redmond, Washington). In yet another embodiment, the system runs in a mainframe environment and It runs on a server environment (UNIX is a registered trademark of X / Open Ltd., Reading, Berkshire, UK). The application is flexible and designed to run in a variety of different environments without affecting any of its core functionality. In some embodiments, the system includes multiple components distributed across multiple computing devices. One or more components may be in the form of computer-executable instructions implemented in a computer-readable medium. The system and processing are not limited to the specific embodiments described herein. Furthermore, the components of each system and each process may be practiced independently and separately from the other components and processes described herein. Each component and process may also be used in conjunction with other component packages and processes.

[0049] The following detailed description illustrates embodiments of this disclosure by way of example, not limitation. This disclosure is intended to have general applicability in industrial, commercial, and academic applications.

[0050] As used herein, elements or steps described in the singular and preceded by the word "a" or "an" should be understood to not exclude multiple elements or steps unless such exclusion is explicitly stated. Furthermore, references to "exemplary embodiments" or "an embodiment" in this disclosure are not intended to be construed as excluding the existence of additional embodiments that also include the described features.

[0051] Figure 1 This is a schematic diagram of an example data collector (DC) platform used to collect digital wallet data from user-initiated digital wallet transactions to determine a user's demographics. The embodiments described herein may relate to transaction card systems, such as payment card payment systems using the Mastercard Exchange Network. The Mastercard Exchange Network is a proprietary communication standard issued by Mastercard International, Inc., for the settlement of funds and the exchange of financial transaction data between financial institutions that are members of Mastercard International. (Mastercard is a registered trademark of Mastercard International, Inc., located in Purchase, New York). The embodiments described herein also relate to a data collector (DC) computing device 150 communicatively coupled to an exchange network computing device 28. The DC computing device 150 is configured to receive digital wallet data from the exchange network computing device 28 and determine a user's demographics based on the received digital wallet data.

[0052] In the exemplary DC platform, a financial institution, referred to as the "issuer" or "issuing bank," issues an account, such as a credit card account, to user 22, which user 22 uses to reimburse purchases from merchant 24. In one embodiment, the user presents a digital wallet to merchant 24 using a user computing device (also known as a card-present transaction). In another embodiment, the user does not present a digital wallet but instead performs a cardless transaction. For example, a cardless transaction can be initiated via a digital wallet application, through a website or portal, via telephone, or any other method that does not require the user to present a physical payment card to merchant 24 (e.g., via scanning a digital wallet).

[0053] To accept payments using transaction cards, merchant 24 establishes an account with a financial institution that is part of a financial payment system. This financial institution is typically referred to as a "merchant bank," "acquiring bank," or "acquiring party." In one embodiment, user 22 uses a transaction card to pay for a purchase at transaction processing device 40 (e.g., a point-of-sale device), and then merchant 24 requests authorization from merchant bank 26 for the purchase amount. This request is typically executed using a point-of-sale terminal that reads user 22's account information from the magnetic stripe, chip, barcode, or embossed characters on the transaction card (e.g., a digital wallet) and communicates electronically with the transaction processing computer of merchant bank 26. Alternatively, merchant bank 26 may authorize a third party to perform transaction processing on its behalf. In this case, the point-of-sale terminal will be configured to communicate with the third party. This third party is typically referred to as a "merchant processor," "acquiring processor," or "third-party processor."

[0054] Using exchange network 28, the merchant processor or the computer of merchant bank 26 will communicate with the computer of issuing bank 30 to determine whether user 22's account 32 is creditworthy and whether user 22's available credit limit covers the purchase. Based on these determinations, the authorization request will be rejected or accepted. If the request is accepted, an authorization code will be issued to merchant 24.

[0055] When an authorization request is accepted, the available credit limit of user 22's account 32 is reduced. Typically, fees for payment card transactions are not immediately posted to user 22's account 32 because certain rules do not allow merchant 24 to charge or "capture" a transaction before shipping goods or delivering services. However, for at least some debit card transactions, fees can be posted at the time of the transaction. When merchant 24 ships or delivers goods or services, merchant 24 captures the transaction through an appropriate data entry process, such as at a point-of-sale terminal. This can include daily approved transactions bundled with standard retail purchases. If user 22 cancels a transaction before it is captured, an "invalid" transaction is generated. If user 22 returns goods after a transaction has been captured, a "credit" transaction is generated. The exchange network 28 and / or issuing bank 30 store transaction card information (such as merchant type, purchase amount, purchase date) in database 120 (e.g., Figure 2 (as shown in the image).

[0056] Following a purchase, a clearing process occurs to transfer additional digital wallet data related to the purchase between the parties to the transaction (such as merchant bank 26, exchange network 28, and issuing bank 30). More specifically, during and / or after the clearing process, additional data (such as purchase time, merchant name, merchant type, purchase information, user account information, transaction type, information about the purchased items and / or services, and / or other suitable information) is associated with the transaction and sent between the parties as digital wallet data, and may be stored by any party to the transaction.

[0057] After a transaction is authorized and cleared, it is settled between Merchant 24, Merchant Bank 26, and Issuing Bank 30. Settlement refers to the transfer of financial data or funds between the accounts of Merchant 24, Merchant Bank 26, and Issuing Bank 30 associated with the transaction. Typically, transactions are captured and accumulated into a “batch,” which is settled in groups. More specifically, transactions are typically settled between Issuing Bank 30 and Exchange Network 28, then between Exchange Network 28 and Merchant Bank 26, and finally between Merchant Bank 26 and Merchant 24.

[0058] As mentioned above, the parties involved in a payment card transaction include Figure 1 The parties shown may include, for example, user 22, merchant 24, merchant bank 26, exchange network 28 (also referred to herein as payment processor 28), issuing bank 30, and / or issuing processor 21.

[0059] Figure 2This is a block diagram of an example data collector (DC) computing platform, in which various computing devices are communicatively coupled to each other via multiple network connections. These network connections can be the Internet, LAN / WAN (Local Area Network / Wide Area Network), or other connections capable of sending data across computing devices. Environment 100 illustrates a data collector (DC) computing device 150 and a database server 116. In one embodiment, the DC computing device 150 and the database server 116 are components of a server system 112. The server system 112 can be a server, a network of multiple computer devices, a virtual computing device, etc. The DC computing device 150 is connected to at least one user computing device 170, a merchant computing device 180, and a publisher computing device 114 via network connection 115.

[0060] In one embodiment, DC computing device 150 is configured to receive digital wallet data from merchant computing device 180 via network connection 115. (See also: ...) Figure 1 As indicated, digital wallet data is generated when a user executes a transaction at a merchant's location. This digital wallet data can be sent between computer devices as digital wallet data messages. In one embodiment, when a user executes a transaction at a merchant computing device 180 associated with a merchant, the digital wallet data for the transaction is sent to server system 112. Server system 112 then sends the digital wallet data to server system 112 with information about... Figure 1 The described method processes digital wallet data and also provides the digital wallet data to the DC computing device 150. The DC computing device 150 is also configured to communicate with the user computing device 170 via an electronic communication channel or method different from the electronic communication channel or method used to transmit the digital wallet data. In an example embodiment, the DC computing device 150 is configured to communicate with the user computing device 170 via electronic communication channel 135.

[0061] Digital wallet data messages may also include transaction amount, transaction date, account data associated with the payment card used to execute the transaction (e.g., primary account number associated with the payment card, card expiration date, card issuer, card security code, etc.), merchant identifier, stock-keeping unit (SKU) data associated with goods or services purchased from the user, etc. In one embodiment, digital wallet data messages also include location data, such as address data, city data, state data, zip code or postal code data, country data, merchant location identifier data, IP address data, MAC address data, etc., as used herein. In another embodiment, digital wallet data messages also include demographic data. Such demographic data may correspond to the user's age, place of origin, gender, etc. DC computing device 150 is configured to receive registration data, store such registration data in memory, further receive digital wallet data as part of a digital wallet transaction initiated by a user, then compare the registration data with the digital wallet data, link the digital wallet data to the registration data, and determine demographic data associated with multiple users of one or more merchants. In one embodiment, DC computing device 150 parses a complete digital wallet data file to search, filter, or otherwise extract demographic data. For example, DC computing device 150 can determine that the digital wallet data file contains an age identifier after parsing the complete digital wallet data file.

[0062] Database server 116 connects to database 120, which contains information about various matters, as described in more detail below. In one embodiment, database 120 is stored on server system 112 and is accessible to potential users of server system 112. In an alternative embodiment, database 120 is stored remotely from server system 112 and may be decentralized. Database 120 may comprise a single database with separate sections or partitions, or it may comprise multiple databases, each separate from the others. Database 120 may store demographic data for each user communicating with DC computing device 150.

[0063] In an example embodiment, DC computing device 150 includes specially designed computer hardware to perform the steps described herein and includes specially designed computer implementation instructions. DC computing device 150 is a specially designed and custom-built computer device configured to perform specific functions for collecting digital wallet data from user-initiated digital wallet transactions, determining the user's demographics (e.g., age or place of origin), and generating merchant recommendations based on demographic and location data (e.g., the restaurants most visited by 30-year-old Americans in Sydney).

[0064] Figure 3This is an extended block diagram of an example embodiment of a server architecture including other computer devices, such as a data collector (DC) computer platform, according to one embodiment of this disclosure. The DC computer platform 100 includes... Figure 2 The components of environment 100 shown in the diagram are the same as those in the diagram. Figure 3 Used with Figure 2 The same labels used for identification are employed. DC computer platform 100 includes server system 112 (similar to...). Figure 2 The DC computing device 150 shown is included. Server system 112 also includes a database server 116, an application server 125, a web server 126, an authentication server 128, a directory server 130, and a mail server 132. Storage device 134 is coupled to database server 116 and directory server 130. Servers 116, 125, 126, 128, 130, and 132 are coupled in a network connection, such as LAN / WAN 136. Additionally, a bank workstation 138 (similar to...) is also included. Figure 2 The issuer computing device 114, the acquiring bank workstation 140, and the third-party processor workstation 142 shown can be coupled to the LAN / WAN 136.

[0065] In the example embodiment, the issuing bank workstation 138, the acquiring bank workstation 140, and the third-party processor workstation 142 use (e.g.) Figure 2 Network connection 115 (as shown) is coupled to LAN / WAN 136. Workstations 138, 140, and 142 are coupled to LAN / WAN 136 via an Internet link or via an intranet. In the example embodiment, DC computing device 150 is coupled to issuing bank workstation 138 and POS computing device 118 (POS computing device 118 may be coupled to, for example, with...). Figure 2 The merchant computing device 180 (as shown) communicates with the user computing device 170. The user computing device 170 is connected to the Internet and may be a smartphone, personal computer, tablet computer, desktop computer, laptop computer, or similar computing device. The DC computing device 150 is configured to receive digital wallet data, including transaction data, metadata, and biometric data, from the POS computing device 118 and the user computing device 170 via the server system 112.

[0066] Each workstation 138, 140, and 142 is a computer with Internet access. While functions performed at a workstation are typically shown as being performed at each of the individual workstations 138, 140, and 142, these functions can actually be performed at one of many personal computers coupled to the LAN / WAN 136. Workstations 138, 140, and 142 are shown associated with individual functions merely to facilitate understanding of the different types of functions that can be performed by an individual with access to the LAN / WAN 136.

[0067] Server system 112 is configured to communicatively couple to various individuals, including employees and third parties 144 (e.g., auditors, developers, merchants, acquirers, issuers, etc.), using an ISP Internet connection 148. Communication in the example embodiment is shown as being performed using the Internet. However, any other wide area network (WAN) type of communication can be used in other embodiments. In other words, the system and processing are not limited to being practiced using the Internet.

[0068] In the example embodiment, any authorized individual with workstation 154 can access DC computer platform 100. At least one of the client systems includes a manager workstation 156 located at a remote location. Workstations 154 and 156 are personal computers with web browsers. Moreover, workstations 154 and 156 are configured to communicate with server system 112. In addition, authentication server 128 communicates with remotely located client systems, including client system 156 using a telephone link. Authentication server 128 is also configured to communicate with other client workstations 138, 140, and 142.

[0069] Figure 4 The illustration shows an example configuration of a user system, such as a user computing device configured to send data to a DC computing device. User system 202 may include, but is not limited to, (…). Figure 2 (See illustration) User computing device 170. In an example embodiment, user system 202 includes a processor 205 for executing instructions. In some embodiments, executable instructions are stored in memory region 210. Processor 205 may include one or more processing units, such as a multi-core configuration. Memory region 210 is any device that allows storage and retrieval of information such as executable instructions and / or writing work. Memory region 210 may include one or more computer-readable media.

[0070] User system 202 also includes at least one media output component 215 for presenting information to user 201. The media output component 215 is any component capable of conveying information to user 201. For example, the media output component 215 may be a display component configured to display component lifecycle data in the form of reports, dashboards, communications, etc. In some embodiments, the media output component 215 includes an output adapter, such as a video adapter and / or an audio adapter. The output adapter is operatively coupled to processor 205 and operatively connected to an output device, such as a display device (liquid crystal display (LCD), organic light-emitting diode (OLED) display, or "e-ink" display), or an audio output device (speaker or headphones).

[0071] In some embodiments, user system 202 includes an input device 220 for receiving input from user 201. Input device 220 may include, for example, a keyboard, pointing device, mouse, stylus, touch-sensitive panel, touchpad, touchscreen, gyroscope, accelerometer, position detector, or audio input device. A single component such as a touchscreen may serve as both an output device for media output component 215 and an input device 220. User system 202 may also include a communication interface 225, which is communicatively connected to, for example, (…). Figure 2 Remote devices such as server system 112 (shown in the diagram). Communication interface 225 may include, for example, a wired network adapter or wireless network adapter or wireless data transceiver used with a mobile phone network, Global System for Mobile Communications (GSM), 3G or other mobile data networks or Global Microwave Access Interoperability (WIMAX).

[0072] Storing in memory region 210 are computer-readable instructions, for example, for providing a user interface to user 201 via media output component 215 and optionally receiving and processing input from input device 220. Among other possibilities, the user interface may include a web browser and client applications. A web browser enables a user, such as user 201, to display and interact with media and other information typically embedded in web pages or websites from server system 112. Client applications allow user 201 to interact with server applications from server system 112.

[0073] Figure 5 The illustration shows, for example Figure 2 The example configuration of server system 301 shown in the figure is a server system 112, which includes a DC computing device 150. Figure 2 (As shown in the diagram). Server system 301 may include, but is not limited to ( Figure 2 The database server 116 shown in the image is either... Figure 2(As shown in the diagram) DC computing device 150. In some embodiments, server system 301 is similar to ( Figure 2 Server system 112 (shown in the image).

[0074] Server system 301 includes a processor 305 for executing instructions. For example, instructions may be stored in memory region 310. Processor 305 may include one or more processing units for executing instructions (e.g., in a multi-core configuration). Instructions can be executed within various operating systems on server system 301, such as UNIX, LINUX, Microsoft... More specifically, the instructions can perform various data operations (e.g., create, read, update, and delete processes) on the data stored in storage device 134. It should also be recognized that various instructions can be executed during initialization when a computer-based method is initiated. Some operations may be required to perform one or more of the processes described herein, while others may be more generalized and / or specific to a particular programming language (e.g., C, C#, C++, Java, or other suitable programming languages).

[0075] Processor 305 is operatively coupled to communication interface 313, enabling server system 301 to communicate with remote devices such as user systems or another server system 301. For example, communication interface 313 can receive communications from issuing computing device 114 via the Internet, such as... Figure 2 As shown.

[0076] Processor 305 may also be operatively coupled to storage device 134. Storage device 134 is hardware suitable for any computer operation of storing and / or retrieving data. In some embodiments, storage device 134 is integrated into server system 301. In other embodiments, storage device 134 is external to server system 301 and is similar to ( Figure 2 (As shown in the diagram) Database 120. For example, server system 301 may include one or more hard disk drives as storage device 134. In other embodiments, storage device 134 is external to server system 301 and can be accessed by multiple server systems 301. For example, storage device 134 may include multiple storage units, such as solid-state drives or hard disks in a redundant array configured with low-cost disks (RAID). Storage device 134 may include storage area network (SAN) and / or network attached storage (NAS) systems.

[0077] In some embodiments, processor 305 is operatively coupled to storage device 134 via storage interface 320. Storage interface 320 is any component capable of providing processor 305 with access to storage device 134. Storage interface 320 may include, for example, an Advanced Technology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, a Small Computer System Interface (SCSI) adapter, a RAID controller, a SAN adapter, a network adapter, and / or any component that provides processor 305 with access to storage device 134.

[0078] Memory region 310 may include, but is not limited to, random access memory (RAM) such as dynamic RAM (DRAM) or static RAM (SRAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and non-volatile RAM (NVRAM). The above memory types are merely exemplary and are therefore not limiting to the types of memory that can be used to store computer programs.

[0079] Figure 6A and Figure 6B This is an example flowchart illustrating the method's flow. Through this method's flow, ( Figure 2 The DC computing device 150 (shown in the diagram) collects digital wallet data from user-initiated digital wallet transactions to determine the user's demographics. In an example embodiment, the DC computing device 150 receives 602 registration data, including user demographic data, from a user's computing device. The DC computing device 150 stores the registration 604 in memory (e.g., a payment processor database). The DC computing device 150 also uses a digital wallet application to receive 606 digital wallet data from the user to execute digital wallet transactions. Subsequently, the DC computing device 150 compares the digital wallet data with the registration data 608, links the digital data 610 to the registration data including the user's demographic data, and determines 612 demographic data associated with multiple users for one or more merchants.

[0080] When registering or setting up a digital wallet application, ( Figure 2 The user computing device 170 (shown in the diagram) creates device registration data. During the registration process, the DC computing device 150 receives 602 registration data, which may include user account data, device data associated with the user computing device 170, and user demographic data. For example, during the registration process, the user may be requested to provide demographic data such as their age and preferred language. Preferred language can help determine the user's country of origin, as many countries have a national language.

[0081] Subsequently, the DC computing device 150 can store the user's demographic data as part of the registration data in (604). Figure 3 (As shown in the diagram) Storage device 134. Device registration data may include some of this demographic and / or other device data that can be shared when the digital wallet is used to execute transactions. For example, device registration data may include device ID, browser type, IP address, user location data, biometric data, preferred language, etc.

[0082] As ( Figure 3 As shown in the diagram, this is part of a digital wallet transaction initiated by user computing device 170 at a point-of-sale (POS) computing device 118 associated with a merchant, where DC computing device 150 receives the digital wallet. POS computing device 118 can be accessed via (… Figure 2 The network connection 115 (shown in the diagram) sends digital wallet data to the processor 305. The digital wallet data may include transaction data, device communication data or metadata, and biometric data associated with transactions and users.

[0083] DC computing device 150 compares digital wallet data received from POS device 118 with registration data stored in storage device 134 608. This comparison can be performed to identify a registered user associated with the received digital wallet data. In doing so, DC computing device 150 can compare user biometric data included in the digital wallet data with a user identifier stored in storage device 134 as part of the registration data. DC computing device 150 can also compare device registration data with device communication data to determine if the user computing device 170 used to send the digital wallet data belongs to a registered user. To perform the comparison, DC computing device 150 can retrieve the user's registration data from storage device 134 to associate this data with the user's digital wallet data. Once the registration data is retrieved, DC computing device 150 compares the registration data with the digital wallet data 608.

[0084] Subsequently, the DC computing device 150 links the user's corresponding digital wallet data 610 to the registration data. More specifically, transaction data in the digital wallet data is linked to demographic data in the registration data. For example, transaction data providing merchant location, purchase time, and type of goods or services purchased is coupled with registration data including the user's age and place of origin.

[0085] By linking digital wallet data to registration data, DC computing device 150 can determine 612 demographic data associated with multiple users for at least one merchant. For example, DC computing device 150 can use the determined demographic data to identify the type of demographic group that frequently visits a merchant's location during a specific time period. DC computing device 150 can also use the determined demographic data to generate 614 merchant recommendations based on the specific demographics (age, country of origin, etc.) of actual visitors to attractions, venues, and / or merchants in these locations.

[0086] In some embodiments, the DC computing device 150 receives a merchant recommendation request from a requester. When a requester requests a merchant recommendation, the DC computing device 150 communicates with the storage device 134 to retrieve augmented data based on the requester's geographic origin and age, and generates 614 or more merchant recommendations based on the retrieved data. The DC computing device 150 sends the results (e.g., one or more recommended merchants) to the requester's computing device. The merchant recommendations can be provided to the requester via SMS text displayed on a webpage or within an application.

[0087] Figure 7 An example configuration of a database 700 and other related computing components within a computing device is shown, which can be used to collect digital wallet data from user-initiated digital wallet transactions to determine the user's demographics. In some embodiments, the computing device 710 is similar to ( Figure 2 Server system 112 (as shown in the diagram). User 702 (such as user operating server system 112) can access computing device 710 to verify user demographics. In some embodiments, database 720 is similar to ( Figure 2 Database 120 is shown in the figure. In an example embodiment, database 720 includes requester data 722, registration data 724, and digital wallet data 726. Requester data 722 may include requester personal data (e.g., address, city, state, zip code or postal code, country, preferred language, demographic data), requester computing device data (e.g., IP address data, MAC address data), and requester input location (e.g., city, state, zip code or postal code, country).

[0088] Registration data 724 may include user personal data (e.g., address, city, state, zip code or postal code, country, phone number, preferred language, account number, demographic data), issuer data, etc. Digital wallet data 726 may include transaction amount, transaction date / time, account data associated with the payment card used to execute the transaction (e.g., primary account number associated with the payment card, card expiration date, card issuer, card security code, etc.), merchant identifier, stock-quantity unit (SKU) data associated with goods or services purchased from the user, user demographic data, etc.

[0089] The computing device 710 also includes a data storage device 730. The computing device 710 further includes a collection component 740, which determines demographic data associated with multiple users for one or more merchants. The collection component 740 can perform, for example... Figure 6A and Figure 6B The comparison 608, linking 610, and / or determining 612 steps are described in the description. The computing device 710 also includes a display component 750 that facilitates the display of data. The computing device 710 also includes a communication component 760 for communicating with user computing devices, publisher computing devices, and vendor computing devices via the Internet using predefined network protocols such as TCP / IP (Transmission Control Protocol / Internet Protocol).

[0090] As will be appreciated based on the foregoing description, the embodiments described above can be implemented using computer programming or engineering techniques, including computer software, firmware, hardware, or any combination or subset thereof, wherein the technical effect is to collect digital wallet data from user-initiated digital wallet transactions to determine the user's demographics. Any such program having computer-readable code means can be implemented or provided in one or more computer-readable media to create a computer program product (i.e., article of manufacture) according to the embodiments discussed in this disclosure. Computer-readable media can be, for example, but not limited to, fixed (hard) drives, floppy disks, optical disks, magnetic tapes, semiconductor memories such as read-only memory (ROM), and / or any transmitting / receiving media (such as the Internet or other communication networks or links). An article of manufacture containing computer code can be made and / or used by executing the code directly from one medium, by copying the code from one medium to another, or by transmitting the code over a network.

[0091] These computer programs (also referred to as programs, software, software applications, "apps," or code) include machine instructions for a programmable processor and can be implemented using high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) used to provide machine instructions and / or data to a programmable processor, including machine-readable media that receive machine instructions as machine-readable signals. However, "machine-readable medium" and "computer-readable medium" do not include transient signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0092] This written description uses examples to disclose the contents of this disclosure, including the best mode, and also enables any person skilled in the art to practice this disclosure, including making and using any device or system and performing any included methods. The patent scope of this disclosure is defined by the claims, but may include other examples that would occur to a person skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that are not different from the literal language of the claims, or if they include equivalent structural elements that are not substantially different from the literal language of the claims.

Claims

1. A computer-based method for generating merchant recommendations using enhanced digital wallet data, the computer-based method being performed using a data collector (DC) computing device comprising at least one processor communicating with at least one memory device, the DC computing device being communicatively coupled to a database of a payment processor associated with an exchange network, the computer-based method comprising: The DC computing device receives registration data from each of a plurality of users of a digital wallet application, each of whom has registered to a corresponding user device. The registration data includes first biometric data and demographic data input by the corresponding user among the plurality of users, wherein the first biometric data of the corresponding user is captured by the corresponding user device using at least one of fingerprint recognition software and facial recognition software, and wherein the registration data also includes a first device identifier that identifies the corresponding user device including the digital wallet application. The DC computing device stores each user's registration data in the at least one memory device; For each of the multiple digital wallet transactions initiated by a candidate user among the plurality of users using the digital wallet application by scanning the digital wallet application at the merchant's point-of-sale device at the merchant's physical location: The DC computing device receives digital wallet data from the payment processor's database, including: account number, transaction amount, merchant identifier, corresponding merchant physical location, second device identifier, and second biometric data of the candidate user captured by the candidate user device using at least one of fingerprint recognition software and facial recognition software. The DC computing device performs the following comparisons: (a) comparing first biometric data in the stored registration data with received second biometric data, and (b) comparing first device identifier in the stored registration data with received second device identifier, to match candidate users with the registration data of registered users among the plurality of users; as well as In the at least one memory device of the DC computing device and based on the matching of registration data of candidate users and registered users, the registration data of registered users is linked with the digital wallet data of candidate users to create enhanced digital wallet data, wherein the linking enhances the digital wallet data by associating the demographic data of registered users with the physical location and merchant identifier of the corresponding merchant with whom the candidate user transacts; The DC computing device receives a merchant recommendation request from the user equipment of the first user among the plurality of users, the merchant recommendation request including the current location of the first user determined by the geolocation component of the first user's user equipment; The DC computing device retrieves the first user's demographic data from the stored registration data; The DC computing device, using the retrieved demographic data and received current location of the first user, filters the enhanced digital wallet data to identify digital wallet transactions that meet the following conditions: i) are made by multiple users other than the first user whose demographic data matches that of the first user, and ii) identify the corresponding additional merchant physical location within a certain distance of the received current location of the first user. The DC computing device generates merchant recommendations for the merchant recommendation request using filtered enhanced digital wallet data. The merchant recommendations identify multiple merchants corresponding to the physical location of the corresponding additional merchant, wherein the filtered enhanced digital wallet data indicates multiple merchants frequently visited by the multiple users other than the first user, which match the demographic data of the first user. as well as The DC computing device sends the merchant recommendation to the user equipment of the first user.

2. The computer-based method of claim 1, wherein the digital wallet data includes at least one item identifier that identifies a product or service associated with each of the plurality of digital wallet transactions.

3. The computer-based method of claim 1, wherein sending the merchant recommendation to the user device of the first user further includes providing the merchant recommendation via at least one of SMS text, web page, and digital wallet application.

4. The computer-based method of claim 1, wherein sending the merchant recommendation to the user equipment of the first user further includes providing the merchant recommendation via a type of electronic communication channel specified by the first user.

5. The computer-based method according to claim 1, wherein the demographic data further includes at least one of the following: the age of the corresponding user, the age range of the corresponding user, the gender of the corresponding user, and the place of origin of the corresponding user.

6. The method of claim 1, wherein matching the demographic data of the first user during the identification of digital wallet transactions further includes matching at least one of the following: the age of the first user, the age range of the first user, the gender of the first user, and the place of origin of the first user.

7. A data collector (DC) computing device for generating merchant recommendations using enhanced digital wallet data, the DC computing device comprising: At least one processor communicating with at least one memory device, the DC computing device being communicatively coupled to a database of a payment processor associated with a switching network, wherein the DC computing device is configured to perform the following operations: Each of a plurality of users of a digital wallet application registered to a respective user device receives registration data, which includes first biometric data and demographic data input by the respective user, wherein the first biometric data of the respective user is captured by the respective user device using at least one of fingerprint recognition software and facial recognition software, and wherein the registration data also includes a first device identifier identifying the respective user device including the digital wallet application. Each user's registration data is stored in the at least one memory device; For each of the multiple digital wallet transactions initiated by a candidate user among the plurality of users using the digital wallet application by scanning the digital wallet application at the merchant's point-of-sale device at the merchant's physical location: The payment processor's database receives digital wallet data including: account number, transaction amount, merchant identifier, corresponding merchant physical location, second device identifier, and second biometric data of the candidate user captured by the candidate user device using at least one of fingerprint recognition software and facial recognition software. The following comparisons are made: (a) comparing first biometric data in the stored registration data with second biometric data received, and (b) comparing first device identifier in the stored registration data with second device identifier received, to match candidate users with the registration data of registered users among the plurality of users; as well as In the at least one memory device of the DC computing device and based on the matching of registration data of candidate users and registered users, the registration data of registered users is linked with the digital wallet data of candidate users to create enhanced digital wallet data, wherein the linking enhances the digital wallet data by associating the demographic data of registered users with the physical location and merchant identifier of the corresponding merchant with whom the candidate user transacts; A merchant recommendation request is received from the user device of a first user among the plurality of users, the merchant recommendation request including the current location of the first user determined by the geolocation component of the first user's user device; Retrieve the demographic data of the first user from the stored registration data; Using the first user's retrieved demographic data and received current location, filter the enhanced digital wallet data to identify digital wallet transactions that meet the following criteria: i) are made by multiple users whose demographic data matches that of the first user, in addition to the first user; and ii) identify the corresponding additional merchant physical location within a certain distance of the received first user's current location. Using the filtered enhanced digital wallet data, a merchant recommendation is generated for the merchant recommendation request. The merchant recommendation identifies multiple merchants corresponding to the physical location of the corresponding additional merchant, wherein the filtered enhanced digital wallet data indicates multiple merchants frequently visited by the multiple users other than the first user, which match the demographic data of the first user. as well as The merchant recommendation is sent to the user device of the first user.

8. The DC computing device of claim 7, wherein the digital wallet data includes at least one item identifier that identifies a product or service associated with each of the plurality of digital wallet transactions.

9. The DC computing device of claim 7, wherein the DC computing device is further configured to send the merchant recommendation via at least one of SMS text, web page, and digital wallet application.

10. The DC computing device of claim 7, wherein the DC computing device is further configured to provide the merchant recommendation via a type of electronic communication channel specified by the first user.

11. The DC computing device of claim 7, wherein the demographic data further includes at least one of the following: the age of the corresponding user, the age range of the corresponding user, the gender of the corresponding user, and the place of origin of the corresponding user.

12. The DC computing device of claim 7, wherein the DC computing device is further configured to match the demographic data of the first user during the identification of a digital wallet transaction by matching at least one of the first user's age, the first user's age range, the first user's gender, and the first user's place of origin.

13. A non-transient computer-readable medium storing computer-executable instructions for generating merchant recommendations using enhanced digital wallet data, the computer-executable instructions causing the DC computing device, when executed by a data collector DC computing device comprising at least one processor communicating with at least one memory device and also communicatively coupled to a payment processor associated with a switching network, to perform the following operations: Each of a plurality of users of a digital wallet application registered to a respective user device receives registration data, which includes first biometric data and demographic data input by the respective user, wherein the first biometric data of the respective user is captured by the respective user device using at least one of fingerprint recognition software and facial recognition software, and wherein the registration data also includes a first device identifier identifying the respective user device including the digital wallet application. Each user's registration data is stored in the at least one memory device; For each of the multiple digital wallet transactions initiated by a candidate user among the plurality of users using the digital wallet application by scanning the digital wallet application at the merchant's point-of-sale device at the merchant's physical location: The payment processor's database receives digital wallet data including: account number, transaction amount, merchant identifier, corresponding merchant physical location, second device identifier, and second biometric data of the candidate user captured by the candidate user device using at least one of fingerprint recognition software and facial recognition software. The following comparisons are made: (a) comparing first biometric data in the stored registration data with second biometric data received, and (b) comparing first device identifier in the stored registration data with second device identifier received, to match candidate users with the registration data of registered users among the plurality of users; as well as In the at least one memory device of the DC computing device and based on the matching of registration data of candidate users and registered users, the registration data of registered users is linked with the digital wallet data of candidate users to create enhanced digital wallet data, wherein the linking enhances the digital wallet data by associating the demographic data of registered users with the physical location and merchant identifier of the corresponding merchant with whom the candidate user transacts; A merchant recommendation request is received from the user device of a first user among the plurality of users, the merchant recommendation request including the current location of the first user determined by the geolocation component of the first user's user device; Retrieve the demographic data of the first user from the stored registration data; Using the first user's retrieved demographic data and received current location, filter the enhanced digital wallet data to identify digital wallet transactions that meet the following criteria: i) are made by multiple users whose demographic data matches that of the first user, in addition to the first user; and ii) identify the corresponding additional merchant physical location within a certain distance of the received first user's current location. Using the filtered enhanced digital wallet data, a merchant recommendation is generated for the merchant recommendation request. The merchant recommendation identifies multiple merchants corresponding to the physical location of the corresponding additional merchant, wherein the filtered enhanced digital wallet data indicates multiple merchants frequently visited by the multiple users other than the first user, which match the demographic data of the first user. as well as The merchant recommendation is sent to the user device of the first user.

14. The non-transient computer-readable medium of claim 13, wherein the digital wallet data includes at least one item identifier that identifies a product or service associated with each of the plurality of digital wallet transactions.

15. The non-transient computer-readable medium of claim 13, wherein the computer-executable instructions further cause the DC computing device to send the merchant recommendation via at least one of SMS text, web page, and digital wallet applications.

16. The non-transient computer-readable medium of claim 13, wherein the computer-executable instructions further cause the DC computing device to provide the merchant recommendation via a type of electronic communication channel specified by a first user.

17. The non-transient computer-readable medium of claim 13, wherein the demographic data further includes at least one of the following: the age of the corresponding user, the age range of the corresponding user, the gender of the corresponding user, and the place of origin of the corresponding user.

18. The non-transient computer-readable medium of claim 13, wherein the computer-executable instructions further cause the DC computing device to match the demographic data of the first user during the identification of a digital wallet transaction by matching at least one of the first user's age, the first user's age range, the first user's gender, and the first user's place of origin.

Images