CN113393324A

CN113393324A - System and method for generating a user-customized message

Info

Publication number: CN113393324A
Application number: CN202110270427.3A
Authority: CN
Inventors: S·西尔瓦拉约; W·吴
Original assignee: Mastercard Asia Pacific Pte Ltd
Current assignee: Mastercard Asia Pacific Pte Ltd
Priority date: 2020-03-12
Filing date: 2021-03-12
Publication date: 2021-09-14
Also published as: SG10202002274TA

Abstract

The present disclosure relates to systems and methods for generating user-customized messages. A transaction data processing server for generating a user-customized message is described, the server comprising a processor, a data storage device and a database. The data storage device stores computer program instructions operable to cause the processor to: (i) receiving transaction data associated with a payment card transaction, the transaction data including a payment card identifier of a payment card associated with the payment card transaction and a transaction attribute of the payment card transaction; (ii) updating a score corresponding to a cardholder profile for a payment card based on transaction attributes for the payment card transaction; (iii) receiving a message generation trigger signal; (iv) generating a trigger signal based on the message, extracting a target cardholder profile from the database; (v) generating a customized message for the target cardholder corresponding to the target cardholder profile using the message generation trigger; and (vi) generating a message payload comprising the customized message and an indication of the payment card identifier associated with the targeted cardholder profile.

Description

System and method for generating a user-customized message

Technical Field

The present disclosure relates to processing transaction data, and more particularly to generating user-customized messages.

Background

With technological advances in the fields of telecommunications and computing, a large number of digital services are provided to users, from entertainment services such as online gaming and video streaming, to financial services such as cryptocurrency and mobile banking, and personal services such as online shopping, real-time digital medical services, and digital tourist guides.

A large amount of data related to users of these digital services is collected by their use of these services. These data can be used well, for example, for learning the user's consumption habits and lifestyle. However, these data typically exist on separate platforms that do not communicate with each other. Thus, it is difficult for a single service provider to utilize all available data to provide seamless service to cardholders. Furthermore, due to the large amount of data, it is a challenge to quickly organize and process data from a large number of digital services to provide real-time or near real-time custom messages to service providers and/or cardholders.

Disclosure of Invention

According to a first aspect of the present invention, there is provided a transaction data processing server for generating a user-customized message. The server comprising a processor, a data storage device, and a database, the database storing a plurality of cardholder profiles, each cardholder profile of the plurality of cardholder profiles comprising a payment card identifier, a plurality of metrics, each metric depending on at least one payment card transaction attribute, and a score associated with each metric of the plurality of metrics, the data storage device storing computer program instructions operable to cause the processor to: (i) receiving transaction data associated with a payment card transaction, the transaction data including a payment card identifier of a payment card associated with the payment card transaction and a transaction attribute of the payment card transaction; (ii) updating a score corresponding to a cardholder profile of a payment card associated with the payment card transaction according to transaction attributes of the payment card transaction; (iii) receiving a message generation trigger signal (trigger); (iv) generating a trigger signal based on the message, extracting a target cardholder profile from the database; (v) generating a customized message for the target cardholder corresponding to the target cardholder profile using the message generation trigger; and (vi) generating a message payload comprising the customized message and an indication of the payment card identifier associated with the targeted cardholder profile.

Accordingly, embodiments of the present invention provide a transaction data processing server for pre-processing transaction data to provide customized messages to cardholders. In particular, a transaction data processing server includes a processor, a data storage device, and a database. A database stores a plurality of cardholder profiles, each cardholder profile of the plurality of cardholder profiles comprising a payment card identifier, a plurality of metrics and a score associated with each metric of the plurality of metrics, each metric being dependent on at least one payment card transaction attribute. The data storage device stores computer program instructions operable to cause a processor to: (i) receiving transaction data associated with a payment card transaction, the transaction data including a payment card identifier of a payment card associated with the payment card transaction and a transaction attribute of the payment card transaction; (ii) updating a score corresponding to a cardholder profile of a payment card associated with the payment card transaction according to transaction attributes of the payment card transaction; (iii) receiving a message generation trigger signal; (iv) generating a trigger signal based on the message, extracting a target cardholder profile from the database; (v) generating a customized message for the target cardholder corresponding to the target cardholder profile using the message generation trigger; and (vi) generating a message payload comprising the custom message and an indication of a payment card identifier associated with the targeted cardholder profile. In this way, the transaction data may be pre-processed by updating the score of the cardholder profile using the transaction attributes of the payment card transaction. By pre-processing the transaction data, this relieves the server of the burden of processing large amounts of data only upon receipt of a message generation trigger or a request from an intermediary server, thus providing a means to better manage the computing resources of the server. In addition, since the transaction data has been pre-processed, the server is able to generate a trigger signal in response to the message, providing the desired customized message in real-time or near real-time. This is important to provide a seamless customer experience to the cardholder as will be explained in the examples below. Furthermore, the transaction data processing server acts as a centralized platform for collating different information about the cardholder through payment transactions performed by the cardholder. This provides an integrated source of information for other service providers to provide customized messages to their targeted cardholders, for example, personalizing rewards or services provided to the targeted cardholders.

Furthermore, embodiments of the present invention can be readily implemented using existing infrastructure, minimizing the cost of performing the above-described operations. The main arrangement required is to provide the transaction data processing server for processing and storing information relating to the transaction data received for the cardholder profile. This can be readily accomplished using existing memory, servers, and/or databases.

The message generation trigger signal may include an indication of a location and an indication of a payment card, the computer program instructions operable to cause the processor to extract the targeted cardholder profile from the database may include instructions to extract the targeted cardholder profile using the indication of the targeted payment card, and the data storage device may further store computer program instructions operable to cause the processor to: (i) identifying a recommendation category based on the target cardholder profile; (ii) sending a recommendation request to a bid repository for bids associated with recommendation categories in proximity to the location; and (iii) receive a recommendation response from the offer store that includes the offer, wherein the message payload further includes an indication of the offer.

The message generation trigger signal may include an indication of a monitoring indicator, an indication of a monitoring time period, and an indication of a monitoring range, and the data storage device may further store computer program instructions operable to cause the processor to: (i) identifying, for each of a plurality of cardholder profiles, a monitoring score associated with a monitoring metric for a monitoring time period; and (ii) determining whether the monitoring score is within the monitoring range, wherein the computer program instructions operable to cause the processor to extract the targeted cardholder profile from the database may include instructions to extract the targeted cardholder profile from the database if the monitoring score is determined to be within the predetermined range.

The message generation trigger signal may include an indication of reward criteria for rewarding the cardholder, and the data storage device may further store computer program instructions operable to cause the processor to: (i) identifying a reward score associated with the reward criteria; and (ii) determining whether the reward score meets the reward criteria, wherein the computer program instructions operable to cause the processor to extract the targeted cardholder profile from the database may comprise instructions to extract the targeted cardholder profile from the database if it is determined that its reward score meets the reward criteria.

The computer program instructions operable to cause the processor to update the score of the cardholder profile may include instructions to increase the score according to a number of payment card transactions performed relative to an indicator associated with the score.

The data storage device may also store computer program instructions operable to cause the processor to analyze transaction data associated with a plurality of payment card transactions performed against the cardholder profile to derive derivative attributes using transaction attributes of the plurality of payment card transactions.

According to a second aspect of the present invention, there is provided a transaction data processing method of generating a user-customized message. The method comprises the following steps: (i) receiving transaction data associated with a payment card transaction, the transaction data including a payment card identifier of a payment card associated with the payment card transaction and a transaction attribute of the payment card transaction; (ii) updating a score corresponding to a cardholder profile of a payment card associated with the payment card transaction according to transaction attributes of the payment card transaction; (iii) receiving a message generation trigger signal; (iv) based on the message generating a trigger signal, extracting a target cardholder profile from a database, the database storing a plurality of cardholder profiles, each cardholder profile of the plurality of cardholder profiles comprising a payment card identifier, a plurality of metrics and a score associated with each metric of the plurality of metrics, each metric depending on at least one payment card transaction attribute; (v) generating a customized message for the target cardholder corresponding to the target cardholder profile using the message generation trigger; and (vi) generating a message payload comprising the customized message and an indication of the payment card identifier associated with the targeted cardholder profile.

The message generation trigger may include an indication of a location and an indication of a payment card, extracting the targeted cardholder profile from the database may include using the indication of the targeted payment card, extracting the targeted cardholder profile, and the method may include: (i) identifying a recommendation category based on the target cardholder profile; (ii) sending a recommendation request to a bid repository for bids associated with recommendation categories in proximity to the location; and (iii) receive a recommendation response from the offer store that includes the offer, wherein the message payload further includes an indication of the offer.

The message generation trigger signal may be received in response to a payment card transaction performed by a targeted cardholder.

The message generation trigger signal may comprise an indication of a monitoring indicator, an indication of a monitoring time period and an indication of a monitoring range, and the method may comprise: (i) identifying, with respect to each of a plurality of cardholder profiles, a monitoring score associated with a monitoring metric for a monitoring time period; and (ii) determining whether the monitoring score is within a monitoring range, wherein extracting the targeted cardholder profile from the database may include extracting the targeted cardholder profile if the monitoring score is determined to be within a predetermined range.

The message generation trigger may include an indication of reward criteria for rewarding the cardholder, and the method may include: (i) identifying a reward score associated with the reward criteria; and (ii) determining whether the reward score meets the reward criteria, wherein extracting the targeted cardholder profile from the database may include extracting the targeted cardholder profile if its reward score is determined to meet the reward criteria.

The message payload may be in the form of a batch file that includes a plurality of custom messages and a plurality of indications of payment card identifiers associated with targeted cardholder profiles.

The message generation trigger may be received in response to the scheduler, and the method may include receiving the message generation trigger from the scheduler at each preset time period.

The method may include resetting the monitoring score or resetting the reward score every preset time period according to the scheduler.

The message generation trigger may be received from an external request from an application interface (API).

Updating the score may include increasing the score according to a number of payment card transactions performed relative to an index associated with the score.

The transaction attributes may include at least one of merchant attributes, transaction amount, and transaction nature.

The method may include receiving feedback associated with a custom message.

The method may include analyzing transaction data associated with a plurality of payment card transactions performed against a cardholder profile to derive derivative attributes using transaction attributes of the plurality of payment card transactions.

According to a third aspect of the invention, a non-transitory computer-readable medium has stored thereon program instructions for causing at least one processor to perform the aforementioned method.

Embodiments of the present invention may be implemented as a network of communication devices (i.e., a "computerized network"). Further embodiments include software applications downloadable into a computer device to facilitate performance of the methods. The software application may be a computer program product that may be stored on a non-transitory computer readable medium on a tangible data storage device, such as a storage device of a server or a storage device within a user device.

Embodiments of the present invention aim to provide a new and useful computer system and computer-implemented method for processing transaction data in order to better manage computing resources and provide a seamless customer experience to cardholders.

Other desirable features and characteristics will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings of the invention.

Brief Description of Drawings

Non-limiting embodiments of the present invention will now be described, for example only, with reference to the following drawings, in which:

FIG. 1 illustrates a computer system for processing transaction data according to an embodiment of the invention;

FIG. 2 shows a block diagram of functional modules of a transaction data processing server including the computer system of FIG. 1, in accordance with an embodiment of the present invention;

FIG. 3 illustrates steps of a transaction data processing method for providing customized messages, which may be performed by the transaction data processing server of FIG. 2, according to an embodiment of the present invention;

fig. 4 illustrates steps of a method for providing a recommended offer to a targeted cardholder according to an embodiment of the invention, which may be performed by the transaction data processing server of fig. 2;

fig. 5 illustrates steps of a method for providing a prompt to a targeted cardholder according to an embodiment of the invention, which may be performed by the transaction data processing server of fig. 2;

fig. 6 illustrates steps of a method for providing rewards to targeted cardholders, which may be performed by the transaction data processing server of fig. 2, in accordance with an embodiment of the invention;

FIG. 7 illustrates steps of a method for receiving feedback according to an embodiment of the invention, which may be performed by the transaction data processing server of FIG. 2;

fig. 8 shows the steps of a method for deriving derived attributes in a cardholder profile, which may be performed by the transaction data processing server of fig. 2, according to an embodiment of the invention;

FIG. 9 illustrates a message flow in a method of processing transaction data using a transaction data processing server included in the computer system of FIG. 1, according to an embodiment of the present invention;

FIG. 10 illustrates a message flow in a method of processing transaction data using a transaction data processing server included in the computer system of FIG. 1 to provide a recommended offer to a cardholder according to an embodiment of the invention;

FIG. 11 illustrates a message flow in a method of processing transaction data using a transaction data processing server included in the computer system of FIG. 1 to provide a prompt to a cardholder according to an embodiment of the invention;

FIG. 12 illustrates message flow in a method of processing transaction data to provide rewards to a cardholder using a transaction data processing server included in the computer system of FIG. 1 in accordance with an embodiment of the invention;

FIG. 13 shows an example of a cardholder profile that may be used by the transaction data processing server of FIG. 2 according to an embodiment of the invention; and

fig. 14 schematically shows the hardware architecture of the transaction data processing server of fig. 2, which may be used in the computer system of fig. 1 to implement a method according to an embodiment of the invention.

Detailed Description

As used herein, the term "transaction data" refers to any data associated with a transaction.

Note that the term "transaction" refers to any form of payment transaction, including transactions conducted using a physical payment card, or cardless payment transactions that may be conducted electronically, where the payment card is not physically present at the time of the payment transaction for review by the merchant. A typical cardless payment transaction may involve a user purchasing a product on a merchant website associated with a merchant server. Other forms of cardless payment transactions are envisaged, such as transfers of funds or bill payments, as long as a transfer of funds between the two parties is involved.

Note that the term "payment card" refers to any noncash payment device associated with a payment account, such as a credit card, debit card, prepaid card, debit card, membership card, promotional card, frequent flyer card, identification card, prepaid card, gift card, and/or any other device that can hold payment account information, such as a mobile phone, smart phone, Personal Digital Assistant (PDA), key fob, transponder device, NFC enabled device, and/or computer. In addition, a "payment card" may exist as an application-based stored value account associated with an electronic wallet service provider associated with an issuer.

Note that the meaning of the term "institution" as used herein is not necessarily limited to only organizations that are legally established as banks, as in some jurisdictions other organizations may be permitted to maintain financial accounts, such as payment card accounts. The mechanism may be one of the following: a bank, a financial technology company, a telecommunications company, or a financial institution.

Note that the term "broker server" refers to any computing resource associated with a third party (e.g., a merchant or institution, etc.) for communicating with the transaction data processing server. A party associated with the intermediary server may register with the transaction data processing server in order to access the transaction data processing server to communicate with the transaction data processing server.

As used in this application, the terms "component," "module," "system," "apparatus," "interface," and the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, or software in execution. For example, a component or module may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. For example, both an application running on a controller and the controller can be a component or a module. One or more component modules can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers.

Furthermore, the claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. For example, the claimed subject matter can be implemented as a computer-readable medium having a computer-executable program embodied therein, comprising a computer program accessible from any computer-readable storage device or storage medium. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips.), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD)), smart cards, and flash memory devices (e.g., card, stick, key drive).

FIG. 1 illustrates a computer system 100 for processing transaction data according to an embodiment of the invention. Computer system 100 includes a conventional payment architecture that includes a cardholder device 102, a payment card 103 associated with a cardholder, a merchant server 104, an acquirer server 106, a payment network server 108, and an issuer server 110. Cardholder device 102 includes any electronic device associated with a cardholder that enables the cardholder to perform a payment transaction. The payment transaction may be performed at a merchant brick and mortar store or at a merchant portal associated with the merchant, and the payment transaction may be performed by the cardholder using the cardholder device 102 or the payment card 103. Cardholder device 102 may be a mobile phone, laptop/notebook, desktop, tablet, Personal Digital Assistant (PDA), key fob, transponder device, NFC enabled device, and/or computer. The merchant server 104 is associated with a merchant. The payment card 103 refers to any form of cashless payment device as defined above. The merchant server 104 may communicate with point-of-sale terminals in the merchant's physical store and/or may provide a merchant portal on which card-less payment transactions may be initiated. Acquirer server 106 is operated by an acquirer institution where the merchant maintains a merchant account to receive funds. Payment network server 108 is associated with a payment network, such as a Banknet payment network operated by mastercard, for facilitating payment transactions between cardholders and merchants. The issuer server 110 is associated with an issuer that maintains at least one cardholder account that may be used to process payment transactions processed by the merchant server 104. In addition, computer system 100 includes a transaction data processing server 112 in communication with payment network server 108, merchant server 104, and cardholder device 102. As will be described in detail below, embodiments of a method for processing transaction data are performed at the transaction data processing server 112 to generate a customized message in response to a message generation trigger. Further, the computer system 100 includes an intermediary server 113. A message generation trigger may be received from the mediating server 113. Broker server 113 may be any computing resource associated with cardholder device 102, merchant server 104, acquirer server 106, issuer server 110, or any partner that uses transaction data processing server 112 to generate customized messages. As shown in fig. 1, broker server 113 is in communication with cardholder device 102, merchant server 104, acquirer server 106, issuer server 110, and transaction data processing server 112. Although the broker server 113 is shown in FIG. 1 as being external to the merchant server 104, the acquirer server 106, and the issuer server 110, in embodiments the broker server 113 may be part of the merchant server 104, the acquirer server 106, and the issuer server 110.

A database for storing relevant data used in embodiments of the present invention is also included in computer system 100. As shown in FIG. 1, the computer system 100 includes a database 114 connected to the transaction data processing server 112. In one embodiment, the computer system 100 also includes an offer store 115 in communication with the transactional data processing server 112. Database 114 may be configured to store data associated with payment transactions processed by payment network server 108. The data may include a plurality of cardholder profiles associated with the processed payment transaction, pre-processed data associated with the cardholder profiles, and/or logic scripts for generating custom messages in response to received trigger signals, among other things. Each cardholder profile includes a payment card identifier, a plurality of metrics, and a score associated with each metric of the plurality of metrics, wherein each metric is dependent upon at least one payment card transaction attribute. An example of a cardholder profile is discussed with reference to FIG. 13. The offer store 115 may be updated with current offers or recommendations for providing offers to cardholders, as exemplified by the method discussed below in connection with fig. 4. Further, a payment network database 116 is connected to the payment network server 108 for storing data related to payment transactions performed using the payment network server 108. The data relating to the payment transactions includes at least transaction attributes associated with each of the payment transactions. The payment network database 116 may also store data related to cardholders and partners (e.g., merchants or financial institutions, etc.) that utilize the payment network server 108 to process payment transactions. Although the database 114 and the payment network database 116 are shown in fig. 1 as external databases, these

databases

114, 116 may also form part of the transaction data processing server 112 and the payment network server 110, respectively. The offer store 115 may also form part of the transactional data processing server 112.

Although only one cardholder device 102, only one payment card 103, and only one merchant server 104 are shown in fig. 1, it should be understood that multiple cardholder devices 102, multiple payment cards 103, and multiple merchant servers 104 associated with respective POS terminals or merchant portals may also form part of computer system 100. Similarly, a plurality of acquirer servers 106 and a plurality of issuer servers 110 may also be in communication with the payment network server 108 and form part of the computer system 100. A plurality of payment network servers 108 may also form part of the computer system 100 such that the transaction data processing server 112 may communicate with the plurality of payment network servers 108. Likewise, a plurality of payment network databases 116 associated with respective payment network servers 108 may also form part of the computer system 100. Further, although only one mediating server 113 is shown in FIG. 1, it should be understood that a plurality of mediating servers 113 may also form part of the computer system 100. In an embodiment, cardholder device 102, merchant server 104, acquirer server 106, and issuer server 110 may each be associated with an broker server 113, with broker server 113 being in communication with transaction data processing server 112.

Communication between cardholder device 102,

servers

104, 106, 108, 110, 112, and

databases

114, 115, 116 may occur over any type of system, such as a Virtual Private Network (VPN), the internet, a local area network and/or a wide area network (LAN and/or WAN), and the like.

Fig. 2 shows a block diagram of functional modules comprising the transaction data processing server 112 according to an embodiment of the invention. As shown in FIG. 2, the transaction data processing server 112 includes a communication module 202, a data processing module 204, an application module 206, a delivery module 208, and a feedback module 210. The communication module 202 allows the transaction data processing server 112 to communicate with the payment network server 108, the broker server 113, the database 114, and the offer repository 115 over a network (e.g., the internet or an intranet). The data processing module 204 is operable to process transaction data received from the payment network server 108, for example to update the scores of the cardholder profile. The application module 206 is operable to interface with the broker server 113 to receive the message generation trigger from the broker server 113, extract the targeted cardholder profile from the database 114, generate a custom message in response to the message generation trigger, and generate a message payload that includes the custom message and an indication of a payment card identifier associated with the targeted cardholder profile. The delivery module 208 is operable to transmit the message payload to the mediating server 113. The feedback module 210 is operable to receive feedback associated with the custom message or message payload, for example, from the mediating server 113.

Fig. 3 illustrates the steps of a transaction data processing method 300 for providing customized messages, which may be performed by the transaction data processing server of fig. 2, according to an embodiment of the present invention.

In step 302, the data processing module 204 of the transaction data processing server 112 receives transaction data associated with a payment card transaction. The transaction data may be received from the payment network server 108 and include a payment card identifier of a payment card associated with the payment card transaction and transaction attributes of the payment card transaction. The transaction data may be received from an external source through a suitable API in communication with the transaction data processing server 112. The payment card identifier may be a payment card number or the name of the holder of the payment card or a unique token associated with the payment card, etc. Once the payment transaction is processed by the payment network server 108, transaction data associated with the payment transaction may be sent from the payment network server 108 to the transaction data processing server 112. The cardholder profile includes a payment card identifier uniquely associated with the cardholder. In some embodiments, the cardholder profile includes a plurality of payment card identifiers, where each of the payment cards is associated with the same cardholder. The cardholder profile includes at least one indicator. Each index is associated with a score. Each score is associated with at least one transaction attribute of the payment transaction. Each transaction attribute may be associated with one or more scores (see, e.g., fig. 13). Examples of transaction attributes include cardholder attributes (e.g., a payment card number used in a payment transaction), merchant attributes (e.g., merchant name, merchant location, merchant type, etc.), payment amount, the nature of the payment transaction (e.g., contactless, credit card payment, debit card payment, etc.), the time and place at which the payment transaction was performed, and so forth. The at least one score/index/indicator may be included in the cardholder profile as desired, and it is typically included at the request of an intermediary server for tracking attributes or characteristics of the cardholder profile (e.g., consumption at a particular merchant, etc.).

In step 304, the data processing module 204 of the transaction data processing server 112 updates the score corresponding to the cardholder profile of the payment card associated with the payment card transaction according to the transaction attributes of the payment card transaction. For example, if the number of contactless transactions for a cardholder is to be tracked, a "contactless score" is introduced in the cardholder profile associated with the cardholder. The data processing module 204 is configured to increase the "contactless score" in the cardholder profile once a contactless transaction is recorded in the transaction data received at the transaction data processing server 112. These scores may be accessible to partners or users registered with the transactional data processing server 112 and may be introduced by partners or registered users to track specific attributes of the cardholder profile that may be of interest. As shown in the example, broadly speaking, the step of updating the score may include increasing the score according to the number of payment card transactions performed relative to the metric associated with the score.

Steps

302 and 304, as described above, are performed continuously so that the cardholder profile is updated periodically. The updating of the score in step 304 may be triggered by the receipt of transaction data in step 302 (e.g., each time the cardholder performs a payment card transaction), or may be triggered periodically as determined by the transaction data processing server 112 or the intermediary server 113 tracking the score.

At step 306, the application module 206 of the transaction data processing server 112 receives the message generation trigger. A message generation trigger may be received from the mediating server 113. The message generation trigger received at the application module 206 may then prompt the application module 206 to execute the particular logic script associated with the message generation trigger in order to perform the necessary steps to generate the customized message associated with the message generation trigger. Different forms of message generation trigger signals are discussed with reference to fig. 4 to 6.

In step 308, the application module 206 of the transaction data processing server 112 generates a trigger signal based on the message received in step 306, extracting the targeted cardholder profile from the database 114. Depending on the requirements associated with the message generation trigger signal, the application module 206 is configured to identify a targeted cardholder profile that meets the criteria set forth by the message generation trigger signal and extract the targeted cardholder profile accordingly.

In step 310, the application module 206 of the transaction data processing server 112 uses the message generation trigger to generate a custom message for the targeted cardholder corresponding to the targeted cardholder profile. Examples of the generated customized message are discussed below with reference to fig. 4 through 6.

In step 312, the application module 206 of the transaction data processing server 112 generates a message payload that includes the custom message and an indication of the payment card identifier associated with the targeted cardholder profile. In an embodiment, the message payload includes a custom message and an indication of a payment card identifier associated with a plurality of targeted cardholder profiles. In this case, the message payload may be in the form of a batch file. The indication of the payment card identifier provides a means for identifying the targeted cardholder to whom the customized message is to be sent. The delivery module 208 of the transaction data processing server 112 may send the message payload to the mediating server 113.

Fig. 4, 5 and 6 illustrate methods according to embodiments involving different messages generating trigger signals that may be received by the transaction data processing server 112.

Fig. 4 illustrates the steps of a method 400 for providing a recommended offer to a targeted cardholder according to an embodiment of the invention, which may be performed by the transaction data processing server 112 of fig. 2. In this embodiment, the message generation trigger signal includes an indication of the location and an indication of the payment card. The message generation trigger signal may be received in response to a payment card transaction performed by a targeted cardholder. The location of the targeted cardholder may be identified using a payment card transaction conducted by the targeted cardholder. For example, when a target cardholder makes a payment using his or her payment card while leaving a train station or public transportation system (e.g., by using an EZ-Link in singapore), the location of the target cardholder may be identified using the location at which the payment card transaction was performed. The location of the targeted cardholder may also be identified using cardholder device 102, for example, via a Global Positioning System (GPS) of cardholder device 102. This may be for a scenario where an electronic payment is made on the cardholder device 102 through an application and the application communicates with the GPS of the cardholder device 102 to extract the location of the targeted cardholder when processing the payment card transaction.

In step 402, the application module 206 of the transaction data processing server 112 extracts the targeted cardholder profile from the database 114 using the indication of the payment card. This step serves to further define step 308 in which the application module 206 of the transaction data processing server 112 is configured to extract the targeted cardholder profile from the database 114 based on the received message generating a trigger signal.

In step 404, the application module 206 of the transaction data processing server 112 identifies a recommendation category based on the targeted cardholder profile. The recommendation may be identified using a score associated with the targeted cardholder profile and may be associated with a high score stored in the targeted cardholder profile. For example, the targeted cardholder may be a cafe fan and a large number of payment card transactions are conducted at the cafe. In this case, the profile of the target cardholder records a high score associated with the cafe, and the application module 206 is configured to recommend the cafe to the target cardholder.

In step 406, the application module 206 of the transactional data processing server 112 sends a recommendation request to the offer store 115 for offers associated with recommendation categories in the vicinity of the location. The application module 206 may be configured to access the offer store 115 to identify relevant services or offers associated with recommended categories in the vicinity of the location. The relevant vicinity of the identified location may be predetermined, and it may be set within a walking distance (e.g., no more than 2 kilometers or no more than 1 kilometer) from the location. Using the example described above, upon determining that the targeted cardholder prefers to go to a cafe, the application module 206 is configured to access the offer store 115 to determine recommended cafes and/or relevant offers for recommended cafes near the location of the targeted cardholder.

In step 408, the application module 206 of the transactional data processing server 112 receives a recommendation response including the offer from the offer store 115. Using the example above, the offer may include a location of the recommended cafe near the identified location. The offer may include a discount coupon for use by the targeted cardholder at the recommended cafe.

Upon receiving the offer from the offer store 115, the application module 206 of the transaction data processing server 112 uses the received offer to generate a custom message for the targeted cardholder and to generate a message payload that includes the custom message and an indication of the payment card identifier associated with the targeted cardholder profile, as described in

steps

310 and 312 above, respectively. The delivery module 208 of the transaction data processing server 112 then sends the message payload to the mediating server 113 for sending the customized message to the targeted cardholder. Using the example described above, once a message payload including an indication of the offer and payment card identifier has been generated, delivery module 208 of transaction data processing server 112 transmits the message payload to broker server 113 (e.g., a server associated with an application (e.g., Samsung Pay API) of cardholder device 112). The broker server 113 may then send the offer to the target cardholder for the target cardholder to utilize the offer.

Fig. 5 illustrates the steps of a method 500 for providing a prompt to a targeted cardholder according to an embodiment of the invention, which may be performed by the transaction data processing server 112 of fig. 2. In this embodiment, the message generation trigger signal includes an indication of a monitoring indicator, an indication of a monitoring time period, and an indication of a monitoring range.

An example of a prompt for a targeted cardholder includes providing a reminder to the targeted cardholder if the targeted cardholder does not perform any payment card transactions for a monitored period of time (e.g., a week). This example is used in the following description of the method 500 as an illustration of the steps performed by the transaction data processing server 112.

In step 502, the application module 206 of the transaction data processing server 112 identifies a monitoring score associated with the monitoring metrics over the monitoring period with respect to each of the plurality of cardholder profiles. Using the example described above, the monitoring score is associated with the number of payment transactions performed by the targeted cardholder over the monitoring period. In an embodiment, rather than identifying a monitoring score for each of the plurality of cardholder profiles stored in database 114, application module 206 identifies a monitoring score for one or some of the plurality of cardholder profiles. In this case, the identity of the target cardholder profile used for monitoring may be included in the received message generation trigger signal. The monitoring period may be a period of six months, three months, two months, one month, two weeks, one week, or the like.

In step 504, the application module 206 of the transaction data processing server 112 determines whether the monitoring score is within the monitoring range. Using the above example, the monitoring range may be set to not more than one. In this case, if the target cardholder does not perform a payment card transaction (i.e., the transaction score is zero) within the monitoring period, the application module 206 determines that the monitoring score is within a monitoring range of no more than one.

In step 506, the application module 206 of the transaction data processing server 112 extracts the targeted cardholder profile from the database 114 if it determines that its monitoring score is within the monitoring range. This step serves to further define step 308 in which the application module 206 of the transaction data processing server 112 is configured to extract the targeted cardholder profile from the database 114 based on the received message generating a trigger signal.

Using the example above, once the application module 206 has determined which of the multiple cardholder profiles has a zero transaction score, the application module 206 extracts the targeted cardholder profiles. In embodiments where predetermined cardholder profiles are selected for monitoring, the application module 206 identifies these predetermined cardholder profiles (e.g., in the form of payment card identifiers) using the identities of these predetermined cardholder profiles provided prior to step 502 (e.g., included in the message generation trigger).

Steps

502 and 504 are then performed to identify the monitoring score in each of these predetermined cardholder profiles and to determine whether the monitoring score in each of the predetermined cardholder profiles is within the monitoring range. Step 506 is then performed to extract the target cardholder profile from the predetermined cardholder profiles if it is determined that the monitoring score is within the monitoring range.

In any case, once the targeted cardholder profile is extracted, the application module 206 of the transaction data processing server 112 generates a custom message for the targeted cardholder associated with the extracted targeted cardholder profile and generates a message payload that includes the custom message and an indication of the payment card identifier associated with the extracted targeted cardholder profile, as described in

steps

310 and 312, respectively, above. The delivery module 208 of the transaction data processing server 112 then sends the message payload to the mediating server 113 for sending the customized message to the targeted cardholder. Using the above example, customizing the message may include prompting the target cardholder to perform a payment card transaction using a payment card associated with the profile. Once the message payload including the customized message and the indication of the payment card identifier has been generated, the delivery module 208 of the transaction data processing server 112 sends the message payload to the mediating server 113. The broker server 113 may then send the customized message to the targeted cardholder.

Fig. 6 illustrates the steps of a method 600 for providing rewards to targeted cardholders, which may be performed by the transaction data processing server 112 of fig. 2, in accordance with an embodiment of the invention. The message generation trigger includes an indication of reward criteria for rewarding the targeted cardholder. The reward criteria may be associated with a reward. In one example, the reward criteria is associated with a $ 50 reward per consumer ranked one hundred times before the week.

In step 602, the application module 206 of the transaction data processing server 112 identifies, for each of a plurality of cardholder profiles, a reward score associated with a reward criterion. Upon receiving the reward criteria, the application module 206 uses the reward criteria to identify a score associated with the reward criteria. In an embodiment, rather than identifying the reward score for each of the plurality of cardholder profiles stored in database 114, application module 206 identifies the reward score for one or some of the plurality of cardholder profiles. In this case, the identity of the cardholder profile used to provide the reward may be included in the received message generation trigger signal. Using the example above, where the reward criteria are associated with rewards of hundreds of consumers ranked one hundred times a week before, (e.g., counting from 12 am each monday), the application module 206 is configured to identify a reward score associated with the transaction amount. The reward score of the cardholder profile may be increased relative to the payment amount of each payment card transaction performed by the cardholder associated with the cardholder profile and may therefore account for the total payout of the cardholder for the cardholder profile. The reward points may also be time tracked according to reward criteria, and in this case the reward points may be tracked for one week and therefore reset at 12 am every monday.

In another embodiment, rather than first identifying the reward points associated with the reward criteria for each of the plurality of cardholder profiles and then tracking the previous week in accordance with the reward criteria, the reward criteria (e.g., the top one hundred consumers ranked within the previous week) is first identified before tracking the associated reward points associated with the reward criteria. Using the same example, for this embodiment, the points associated with the previous week may be identified and extracted for each cardholder profile according to reward criteria, then the reward points for each cardholder profile for that week are tabulated, and the cardholder profiles are sorted to identify cardholder profiles with a previous one hundred reward points.

In step 604, the application module 206 of the transaction data processing server 112 determines whether the reward score meets the reward criteria. Using the example above, the application module 206 may determine the reward score for each of the plurality of cardholder profiles for the previous week and rank the reward scores for each of the plurality of cardholder profiles to identify which of the profiles are in the previous hundred (e.g., the previous hundred scores associated with the transaction amount).

In step 606, the application module 206 of the transaction data processing server 112 extracts the targeted cardholder profile from the database 114 if it is determined that its reward score meets the reward criteria. Using the example above, after the reward score has been identified for each of the plurality of cardholder profiles, the application module 206 is configured to extract one hundred cardholder profiles that meet the reward criteria. This step serves to further define step 308 in which the application module 206 of the transaction data processing server 112 is configured to extract the targeted cardholder profile from the database 114 based on the received message generating a trigger signal.

Once the targeted cardholder profile is extracted, the application module 206 of the transaction data processing server 112 generates a custom message for the targeted cardholder associated with the extracted targeted cardholder profile and generates a message payload that includes the custom message and an indication of the payment card identifier associated with the extracted targeted cardholder profile, as described in

steps

310 and 312, respectively, above. The delivery module 208 of the transaction data processing server 112 then sends the message payload to the mediating server 113 for sending the customized message to the targeted cardholder. According to the above example, the customized message may include a notification to the targeted cardholder that he/she has won a prize of $ 50 because he/she is one of the first hundred consumers in the week. Once the target cardholder profile associated with the previous one hundred reward points has been extracted, the delivery module 208 sends the message payload to the broker server 113. The broker server 113 may then award $ 50 to each of the targeted cardholders associated with the one hundred targeted cardholder profiles accordingly. For example, in this case, the message payload may be sent to the mediating server in the form of a batch file. The batch file may be placed in a secure folder at the mediating server or in a secure folder in the database 114 accessible by the mediating server.

In a second example, the reward criteria is associated with a $ 50 reward for a targeted cardholder who trades three times in hong Kong. In this case, the message generation trigger signal includes an indication of the payment card used to identify the target cardholder profile. Using the method 600 described above, the application module 206 identifies, in step 602, reward points associated with reward criteria. In this case, the reward score may be a score associated with the number of payment transactions conducted in hong kong. In this particular example, in step 604, the application module 206 determines whether the reward score associated with the targeted cardholder profile meets the reward criteria. If it is determined that its reward score meets the reward criteria, the application module 206 of the transaction data processing server 112 extracts the targeted cardholder profile from the database 114. Once the targeted cardholder profile is extracted, the application module 206 of the transaction data processing server 112 generates a custom message for the targeted cardholder associated with the extracted targeted cardholder profile and generates a message payload that includes the custom message and an indication of the payment card identifier associated with the extracted targeted cardholder profile, as described in

steps

310 and 312, respectively, above. In this case, the customized message may include a notification to the targeted cardholder that he/she has won a prize of $ 50 because three payment card transactions have been conducted in hong kong.

In some embodiments, the application module 206 monitors the progress of the reward score so that a custom message and message payload may be generated and the message payload is then sent to the cardholder via the intermediary server 113 to update the targeted cardholder with his or her progress in obtaining the reward. For example, once the application module 206 determines that the targeted cardholder has made a first payment transaction in hong Kong using the reward score, the delivery module 208 is configured to include a customized message "welcome to hong Kong! This is your first transaction in hong kong "message payload is sent to the mediating server 113 for sending to the targeted cardholder. In a similar manner, upon determining that the targeted cardholder has made a second transaction in hong Kong, the delivery module 208 is configured to send a message payload to the intermediary server 113 that includes a customized message "you are doing your second transaction in hong Kong and get a $ 50 reward for doing another transaction" to send to the targeted cardholder. Upon determining that the targeted cardholder makes a third transaction in hong kong, the delivery module 208 is configured to send a message payload to the broker server 113 that includes a custom message "congratulate you, you are eligible for a cashback award of $ 50" to send to the targeted cardholder.

In some embodiments, the trigger signal is generated in response to the scheduler receiving the message. In this case, the application module 206 of the transaction data processing server 112 receives the message generation trigger signal from the dispatcher at every preset time period. The preset time period may be determined by the mediation server 113. The dispatcher may reside in the transaction data processing server 112 or with the intermediary server 113. Where the scheduler resides at the transaction data processing server 112, the transaction data processing server 112 is configured to set the scheduler in response to a preset time period received from the broker server 113 (e.g., a trigger signal is generated via an initial message received). Using the example of awarding a $ 50 prize per week to the first one hundred consumers, in this case, the scheduler may be configured to send a message generation trigger to the application module 206 at the same time per week (e.g., 12 am every monday), so that the application module 206 may extract the relevant target cardholder profile associated with the message generation trigger for sending the customized message. In some embodiments, the data processing module 204 of the data processing server 112 is configured to reset the monitoring score or reward score for each preset time period according to a scheduler.

In some embodiments, the trigger signal is generated from an external request received message from an application interface (API) via the intermediary server 113. For example, whenever a targeted cardholder performs a payment card transaction using the Samsung Pay application in cardholder device 102, a message generation trigger related to providing recommendations may be received from broker server 113 associated with the Samsung Pay API of cardholder device 102.

As described above, the message generation trigger signal may take a variety of forms, and the application module 206 of the transaction data processing server 112 may be configured accordingly to accommodate different forms of message generation trigger signals, for example, as shown in fig. 4-6. In an embodiment, the steps taken by the application module 206 may be customized using specific logic scripts to extract relevant targeted cardholder profiles for customized messages to be sent to targeted cardholders associated with these extracted targeted cardholder profiles. In another embodiment, specific logic scripts may be used to customize the steps taken by the application module 206 to determine whether the selected cardholder profile is eligible for rewards or whether reminders need to be sent. In some embodiments, the plurality of cardholder profiles stored in database 114 is created in response to a request received from an intermediary server 113 associated with a merchant or financial institution or the like that wishes to conduct a particular activity using the data processing capabilities of transaction data processing server 112. In this case, the broker server 113 may provide a cardholder list (e.g., a list of payment card numbers associated with the cardholder list) to the data processing server 112 to establish a cardholder profile for updating and monitoring. In some embodiments, multiple cardholder profiles may be associated with registered users on the payment network server 108, and these cardholder profiles are established and stored in the database 114 whenever transaction data associated with these registered users is received at the transaction data processing server 112.

Note that the mediating server 113 may have access to specific information, such as the location of the targeted cardholder in the scenario described with reference to fig. 4. However, the intermediary service 113 may not be able to obtain details of all transactions conducted by the cardholder. Embodiments of the present disclosure allow data from multiple sources to be combined to provide a customized message to a cardholder, which is not possible using data from one source alone.

Fig. 7 illustrates the steps of a method 700 for receiving feedback according to an embodiment of the invention, which may be performed by the transaction data processing server 112 of fig. 2.

In step 702, the feedback module 210 of the transaction data processing server 112 receives feedback associated with the custom message. Feedback may be provided by the targeted cardholder who has received the customized message and the feedback may be received by the feedback module 210 via the intermediary server 113. The feedback may relate to whether the targeted cardholder utilized the recommendation or reward. The feedback may be associated with the quality of the customized message provided to the targeted cardholder. In the example described above with reference to fig. 4, where a cafe near a location associated with the targeted cardholder is recommended to the targeted cardholder, the feedback from the targeted cardholder may include the recommended relevance. For example, a recommendation for a cafe may be related to a location (e.g., near a shopping area rather than an office location, etc.) or within a certain time period of the day (e.g., tea hours of drinking from 3 pm to 5 pm).

Fig. 8 shows the steps of a method 800 for deriving derived attributes in a cardholder profile, which may be performed by the transaction data processing server 112 of fig. 2, according to an embodiment of the invention. Another score associated with the derived attribute may also be included in the cardholder profile.

In step 802, the data processing module 204 of the transaction data processing server 112 analyzes transaction data associated with a plurality of payment card transactions performed against a cardholder profile to derive derived attributes using transaction attributes of the plurality of payment card transactions. For example, by analyzing the time, location, and type of payment transaction (each of which may be considered transaction attributes), the data processing module 204 may calculate the cardholder's transaction pattern or lifestyle pattern. For example, a cardholder may regularly conduct transactions in an area on a weekday around lunch hours (e.g., 12 pm to 2 pm). The data processing module 204 may be able to use the type of payment transaction (e.g., the type of merchant associated with the restaurant), the time at which the payment transaction was processed, and the location of the payment transaction to infer the area in which the cardholder may be working. In this case, the derived attributes may be associated with the cardholder's workplace. The derived attributes may be traced back to payment transactions deemed to be associated with the cardholder's workplace. In this case, when the transaction data is received at the transaction data processing server 112, another score associated with the derived attribute described above (and the derived attribute associated with the cardholder's workplace) may be formed and then updated accordingly. To provide one example, a message generation trigger associated with a relevant restaurant that recommends business lunch to the targeted cardholder may use a further score associated with the targeted cardholder's workplace to determine which relevant restaurant to recommend.

Fig. 9 illustrates message flows in a method 900 of processing transaction data using a transaction data processing server 112 included in the computer system 100 of fig. 1, according to an embodiment of the present invention. As described above, the mediating server 113 may be any third party computing resource that communicates with the transaction data processing server 112 to send message generation triggers to the transaction data processing server 112 and receive customized messages from the transaction data processing server 112.

In step 902, the data processing module 204 of the transaction data processing server 112 receives transaction data from the payment network server 108. The transaction data includes a payment card identifier of a payment card associated with the payment card transaction and transaction attributes of the payment card transaction. Upon receiving the transaction data in step 902, the data processing module 204 of the transaction data processing server 112 updates the score of the cardholder profile corresponding to the payment card associated with the payment card transaction according to the transaction attributes of the payment card transaction in step 904. The intermediary server 113 (e.g., a partner or a user registered with the transaction data processing server 112) may access the score.

In step 906, the application module 206 of the transaction data processing server 112 receives the message generation trigger signal from the mediating server 113. The message generation trigger received at the application module 206 may then prompt the application module 206 to execute the particular logic script associated with the message generation trigger in order to perform the necessary steps to generate the customized message associated with the message generation trigger. Different forms of trigger signals are discussed with reference to fig. 4 to 6. In step 908, the application module 206 of the transaction data processing server 112 generates a trigger signal based on the message received in step 906, extracting the targeted cardholder profile from the database 114. Depending on the requirements associated with the message generation trigger signal, the application module 206 determines the targeted cardholder profile that meets the criteria set forth by the message generation trigger signal and extracts the targeted cardholder profile accordingly. In step 910, the application module 206 of the transaction data processing server 112 uses the message generation trigger to generate a custom message for the targeted cardholder corresponding to the targeted cardholder profile. In step 912, the application module 206 of the transaction data processing server 112 generates a message payload that includes the custom message and an indication of the payment card identifier associated with the targeted cardholder profile. In step 914, the delivery module 208 of the transaction data processing server 112 sends the message payload to the mediating server 113.

Fig. 10 illustrates a message flow in a method 1000 according to an embodiment of the invention, the method 1000 for processing transaction data using a transaction data processing server 112 included in the computer system 100 of fig. 1 to provide a recommended offer to a targeted cardholder.

In step 1002, the application module 206 of the transaction data processing server 112 receives a message generation trigger signal from the mediating server 113. The message generation trigger signal includes an indication of the location and an indication of the payment card. In step 1004, the application module 206 of the transaction data processing server 112 extracts the targeted cardholder profile from the database 114 using the indication of the payment card received in step 1002. In step 1006, the application module 206 of the transaction data processing server 112 identifies a recommendation category based on the targeted cardholder profile. The recommendation category may be identified using a score associated with the target cardholder profile. In step 1008, the application module 206 of the transactional data processing server 112 sends a recommendation request to the offer store 115 for offers associated with recommendation categories in the vicinity of the location. In step 1010, the application module 206 of the transactional data processing server 112 receives a recommendation response including the offer from the offer store 115. In step 1012, the application module 206 of the transaction data processing server 112 uses the message generation trigger to generate a custom message for the targeted cardholder corresponding to the targeted cardholder profile. The custom message includes the offer received from offer store 115 in step 1010. In step 1014, the application module 206 of the transaction data processing server 112 generates a message payload that includes the custom message and an indication of the payment card identifier associated with the targeted cardholder profile. In step 1016, the delivery module 208 of the transaction data processing server 112 sends the message payload to the brokering server 113 for sending the customized message to the targeted cardholder associated with the targeted cardholder profile.

Fig. 11 illustrates a message flow in a method 1100 of processing transaction data to provide a prompt to a targeted cardholder using the transaction data processing server 112 included in the computer system 100 of fig. 1, according to an embodiment of the invention.

In step 1102, the application module 206 of the transaction data processing server 112 receives a message generation trigger from the mediating server 113. The message generation trigger signal includes an indication of a monitoring indicator, an indication of a monitoring time period, and an indication of a monitoring range. In step 1104, the application module 206 of the transaction data processing server 112 identifies a monitoring score associated with the monitoring metrics for the monitoring period with respect to each of the plurality of cardholder profiles. In step 1106, the application module 206 of the transaction data processing server 112 determines whether the monitoring score is within the monitoring range. In step 1108, if it is determined that its monitoring score is within the monitoring range, the application module 206 of the transaction data processing server 112 extracts the targeted cardholder profile from the database 114. In step 1110, the application module 206 of the transaction data processing server 112 uses the message generation trigger to generate a custom message for the targeted cardholder corresponding to the targeted cardholder profile. The customized message includes a prompt for the targeted cardholder to perform a payment card transaction using a payment card associated with the profile. In step 1112, the application module 206 of the transaction data processing server 112 generates a message payload including the custom message and an indication of the payment card identifier associated with the targeted cardholder profile. In step 1114, the delivery module 208 of the transaction data processing server 112 sends the message payload to the broker server 113 for sending the customized message to the targeted cardholder associated with the targeted cardholder profile.

Fig. 12 illustrates message flow in a method 1200 for processing transaction data to provide an incentive to a targeted cardholder using the transaction data processing server 112 included in the computer system 100 of fig. 1, in accordance with an embodiment of the present invention.

In step 1202, the application module 206 of the transaction data processing server 112 receives a message generation trigger signal from the mediating server 113. The message generation trigger includes an indication of reward criteria for rewarding the targeted cardholder. The reward criteria may be associated with a reward. In step 1204, the application module 206 of the transaction data processing server 112 identifies, for each of the plurality of cardholder profiles, a reward score associated with the reward criteria. In step 1206, the application module 206 of the transaction data processing server 112 determines whether the reward score meets the reward criteria. In step 1208, if it is determined that its reward score meets the reward criteria, the application module 206 of the transaction data processing server 112 extracts the targeted cardholder profile from the database 114. In step 1210, the application module 206 of the transaction data processing server 112 uses the message generation trigger to generate a custom message for the targeted cardholder corresponding to the targeted cardholder profile. The custom message includes a notification to the targeted cardholder that he/she has won the reward. In step 1212, the application module 206 of the transaction data processing server 112 generates a message payload including the custom message and an indication of the payment card identifier associated with the targeted cardholder profile. In step 1214, the delivery module 208 of the transaction data processing server 112 sends the message payload to the broker server 113 for sending the customized message to the targeted cardholder associated with the targeted cardholder profile.

Fig. 13 shows an example of a cardholder profile 1300 that may be used by the transaction data processing server 112 of fig. 2 according to an embodiment of the invention.

Cardholder profile 1300 is associated with profile identifier 1302. This may be a payment card identifier (e.g., payment card number) associated with the cardholder of the cardholder profile. The cardholder profile comprises a plurality of scores, wherein each score is associated with each metric of a plurality of metrics, each metric depending on at least one transaction attribute of the transaction data received from the payment network server 108. The transaction data may be associated with all payment card transactions (shown in transaction parameters 1303) performed using the payment card associated with the payment card number 1302. In some embodiments, a range of payment card transactions or a subset of all payment card transactions may be defined for updating the cardholder profile 1300. The illustrated cardholder profile 1300 includes a plurality of

metrics

1304, 1306, 1308, 1310, 1312, 1314, 1316. These indices may be used to classify the scores. In the present embodiment as shown in FIG. 13, the metrics include an industry score 1304, a custom score 1306, and a merchant score 1308. Associated with each metric may be other metrics. In this embodiment, other metrics include "dining room" 1310, "grocery store" 1312, "automotive fuel" 1314 and "other transportation fuels" 1316. At least one score may be input for each of these metrics. For example, for the index "dining room" 1310, the score may be associated with the number of payment card transactions performed by the cardholder associated with the merchant type "restaurant".

As shown in fig. 13, in the present embodiment, a row of twenty-four parameters is associated with the index "dining room" 1310. However, the number of parameters associated with each index may be adjusted accordingly. Each parameter may be associated with a number of weeks under the index "dining room" 1310. For example, w1 may represent the score for the index "dining room" 1310 in week 1, w2 may represent the score for the index "dining room" 1310 in week 2, and so on. Thus, each of the twenty-four parameters from "w 1, w2, w3 … w 24" represents a fraction of a week up to a total of twenty-four weeks. In other words, for a cardholder profile 1300 as shown in fig. 13, a total of twenty-four points may be recorded for the index "dining room" 1310. Thus, these twenty-four scores are a record of scores associated with "dining room" 1310 over twenty-four weeks. In one embodiment, once all twenty-four parameters are populated, the week 25 score may be used to replace the score of w1, the week 26 score may be used to replace the score of w2, and so on, such that the score of the index "dining room" 1310 is continuously updated. In another embodiment, once all twenty-four parameters have been filled, all twenty-four parameters may be cleared to generate a new set of bins of "w 1, w2, w3 … … w 24". So that the first twenty-four week records are not saved in the cardholder profile 1300. This is similar for the indices "grocery store" 1312, "automotive fuel" 1314 and "other transportation fuels" 1316, as shown in FIG. 13.

It should be appreciated that the logic used to calculate, maintain, and refresh the scores in the above embodiments is customizable and not hard coded within the system of the transaction data processing server 112. In yet another embodiment, the score associated with the index "dining room" 1310 may be increased by 1 for each incoming transaction associated with a restaurant/cafe. The score may be an aggregate score on a weekly scale (e.g., week 1, week 2 … …, week X), where the number of weeks (e.g., up to X) may be coded and customized within the system. Scores may be aggregated over the following X weeks. For example, after each of X weeks, the score is refreshed and replaced so that the score is only a total score of X total times for that week.

Similarly, the illustrated metrics for the customized score 1306 may be associated with metrics such as "contactless," coffee transaction, "" movie transaction, "and" grocery transaction. As described above, each of these metrics is also associated with a row of twenty-four parameters, and they can be edited in a similar manner.

Another example of tracking the scores in cardholder profile 1300 is shown relative to the index "Merchant score" 1308. The index "merchant score" 1308 may be associated with other indices relating to merchant names such as "McD" 1317, "XX" 1318, and "YY" 1319 as shown. For each of these merchants, there is a counter (i.e., a score) that tracks the number of payment transactions performed at each of these merchants. For example, as shown in FIG. 10, the count 1320 for "McD" 1317 is 50.

Fig. 13 shows an example of a cardholder profile 1300. A plurality of these cardholder profiles may be stored in database 114. In an embodiment, upon receiving the transaction data from the payment network server 108, the data processing module 204 of the transaction data processing server 112 updates the relevant scores in the cardholder profile 1300 using the transaction attributes associated with the transaction data. The parameters and/or counts as described above may then be updated accordingly. Two metrics may be associated with a transaction attribute. For example, if a payment transaction is processed for merchant "McD" 1317, the count 1320 associated with the index "merchant name:" McD "" and the associated score associated with the index "dining room" 1310 may be updated accordingly.

Fig. 14 is a block diagram illustrating a technical architecture of the transaction data processing server 112 according to an embodiment of the present invention. The technical architecture of the transaction data processing server 112 is used to perform the steps of the exemplary method as described above. Typically, these methods are implemented by a plurality of computers, each having a data processing unit. The block diagram shown in FIG. 14 illustrates a technical architecture of a computer suitable for implementing one or more embodiments herein.

The technical architecture includes a processor 1402 (which may be referred to as a central processor unit or CPU), the processor 1402 communicating with storage devices including a secondary memory 1404 (such as a disk drive), a Read Only Memory (ROM)1406, and a random access memory 1408 (RAM). The processor 1402 may be implemented as one or more CPU chips. The technical architecture may further include input/output (I/O) devices 1410 and system connectivity or network devices 1412.

The secondary storage 1404 is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM 1408 is not large enough to accommodate all working data. Secondary storage 1404 may be used to store programs that are loaded into RAM 1408 when such programs are selected for execution. In this embodiment, secondary memory 1404 has a communication module 202, a data processing module 204, an application module 206, a delivery module 208, and a feedback module 210, including non-transitory instructions that are operated on by processor 1402 to perform various operations of the inventive method. As shown in fig. 14, the

modules

202, 204, 206, 208, 210 are different modules that perform the respective functions implemented by the transaction data processing server 112. It should be understood that the boundaries between these modules are merely illustrative and that alternative embodiments may merge modules or alternatively divide module functionality. For example, the modules discussed herein may be broken down into sub-modules to be executed as multiple computer processes, and optionally on multiple computers. Furthermore, alternative embodiments may combine multiple instances of a particular module or sub-module. It should also be understood that although software implementations of

modules

202, 204, 206, 208, 210 are described herein, these modules may alternatively be implemented as one or more hardware modules (e.g., field programmable gate arrays or application specific integrated circuits) including circuits that implement functional equivalents to software implementations. The ROM 1406 is used to store instructions and perhaps data that are read during program execution. The secondary memory 1404, ROM 1406, and/or RAM 1408 may be referred to in some instances as a computer-readable storage medium and/or a non-transitory computer-readable medium.

I/O devices 1410 may include printers, video monitors, Liquid Crystal Displays (LCDs), plasma displays, touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, or other input devices.

The system connection or network device 1412 may take the form of: modems, modem banks, ethernet cards, Universal Serial Bus (USB) interface cards, serial interfaces, token ring cards, Fiber Distributed Data Interface (FDDI) cards, Wireless Local Area Network (WLAN) cards, radio transceiver cards that facilitate radio communications using protocols such as Code Division Multiple Access (CDMA), global system for mobile communications (GSM), Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), Near Field Communications (NFC), Radio Frequency Identification (RFID), and/or other air interface protocols, radio transceiver cards, and other system devices. These system connectivity or network devices 1412 may enable the processor 1402 to communicate with the internet or one or more intranets. With such system connectivity, it is contemplated that the processor 1402 might receive information from the system, or might output information to the system in the course of performing the above-described method operations. Such information, which is typically represented as a sequence of instructions to be executed using processor 1402, may be received from and output to the system, for example, in the form of a computer data signal embodied in a carrier wave.

The processor 1402 executes instructions, code, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk-based systems may all be considered secondary storage 1404), flash drive, ROM 1406, RAM 1408, or system connectivity or network device 1412. Although only one processor 1402 is shown, multiple processors may be present. Thus, while instructions may be discussed as being executed by a processor, instructions may be executed concurrently, serially, or by one or more processors.

Although the technical architecture is described with reference to a computer, it should be understood that the technical architecture may be formed by two or more computers in communication with each other that cooperate to perform a task. For example, but not by way of limitation, an application may be partitioned in a manner that allows instructions of the application to be processed concurrently and/or in parallel. Alternatively, the data processed by the application may be partitioned in a manner that allows for concurrent and/or parallel processing of different portions of the data set by two or more computers. In one embodiment, virtualization software may be used by a technical architecture to provide functionality of multiple servers that are not directly bound to multiple computers in the technical architecture. In one embodiment, the functionality disclosed above may be provided by executing an application and/or multiple applications in a cloud computing environment. Cloud computing may include providing computing services via system connectivity using dynamically extensible computing resources. The cloud computing environment may be established by an enterprise and/or may be leased from a third party provider as needed.

It should be appreciated that at least one of CPU 1402, ROM 1406, and RAM 1408 has been altered by programming and/or loading executable instructions onto the technical architecture, converting the technical architecture in part into a specific machine or device having the novel functionality of the present teachings. The functions implemented by loading executable software into a computer can be converted into hardware implementation by well-known design rules, which is the basis of the fields of electrical engineering and software engineering.

While the foregoing description has described exemplary embodiments, those skilled in the art will understand that many modifications may be made to the embodiments within the scope of the present invention as defined by the claims. Furthermore, features from one or more embodiments may be mixed and matched with features of one or more other embodiments.

Claims

1. A transaction data processing server for generating a user-customized message, the server comprising a processor, a data storage device, and a database, the database storing a plurality of cardholder profiles, each cardholder profile of the plurality of cardholder profiles comprising a payment card identifier, a plurality of metrics and a score associated with each metric of the plurality of metrics, each metric being dependent on at least one payment card transaction attribute, the data storage device storing computer program instructions operable to cause the processor to:

receiving transaction data associated with a payment card transaction, the transaction data including a payment card identifier of a payment card associated with the payment card transaction and a transaction attribute of the payment card transaction;

updating a score of a cardholder profile corresponding to the payment card associated with the payment card transaction according to the transaction attributes of the payment card transaction;

receiving a message generation trigger signal;

extracting a target cardholder profile from the database based on the message generation trigger signal;

generating a customized message for a target cardholder corresponding to the target cardholder profile using the message generation trigger signal; and

generating a message payload comprising the custom message and an indication of the payment card identifier associated with the targeted cardholder profile.

2. The server of claim 1, wherein the message generation trigger signal comprises an indication of a location and an indication of the targeted payment card, the computer program instructions operable to cause the processor to extract the targeted cardholder profile from the database comprise instructions to extract the targeted cardholder profile using the indication of the targeted payment card, and the data storage device further stores computer program instructions operable to cause the processor to:

identifying a recommendation category based on the targeted cardholder profile;

sending a recommendation request to a bid repository for bids associated with the recommended categories in proximity to the location; and

receiving a recommendation response from the offer store containing the offer,

wherein the message payload further comprises an indication of the offer.

3. The server of claim 1, wherein the message generation trigger signal comprises an indication of a monitoring metric, an indication of a monitoring time period, and an indication of a monitoring range, the data storage device further storing computer program instructions operable to cause the processor to:

identifying, with respect to each of the plurality of cardholder profiles, a monitoring score associated with the monitoring metric for the monitoring time period; and

determining whether the monitoring score is within the monitoring range,

wherein the computer program instructions operable to cause the processor to extract the targeted cardholder profile from the database comprise instructions to extract the targeted cardholder profile from the database if the monitoring score of the targeted cardholder profile is determined to be within a predetermined range.

4. The server of claim 1, wherein the message generation trigger signal comprises an indication of reward criteria for rewarding a cardholder, the data storage device further storing computer program instructions operable to cause the processor to:

identifying, for each cardholder profile in the plurality of cardholder profiles, a reward score associated with the reward criteria; and

determining whether the reward score satisfies the reward criteria,

wherein the computer program instructions operable to cause the processor to extract the targeted cardholder profile from the database comprise instructions to extract the targeted cardholder profile from the database if it is determined that the reward score for the targeted cardholder profile meets the reward criteria.

5. The server of any preceding claim, wherein the computer program instructions operable to cause the processor to update the score of the cardholder profile comprise instructions to increase the score by one for each payment card transaction performed relative to an indicator associated with the score.

6. The server of any preceding claim, wherein the data storage device further stores computer program instructions operable to cause the processor to analyze transaction data associated with a plurality of payment card transactions performed against the cardholder profile to derive derivative attributes using transaction attributes of the plurality of payment card transactions.

7. A transaction data processing method of generating a user-customized message, the method comprising:

receiving a message generation trigger signal;

based on the message generating a trigger signal, extracting a target cardholder profile from a database, the database storing a plurality of cardholder profiles, each cardholder profile of the plurality of cardholder profiles comprising a payment card identifier, a plurality of metrics and a score associated with each metric of the plurality of metrics, each metric depending on at least one payment card transaction attribute;

8. The method of claim 7, wherein the message generation trigger includes an indication of a location and an indication of a payment card, extracting the targeted cardholder profile from the database includes extracting the targeted cardholder profile using the indication of a targeted payment card, and the method further comprises:

identifying a recommendation category based on the targeted cardholder profile;

receiving a recommendation response from the offer store containing the offer,

wherein the message payload further comprises an indication of the offer.

9. The method of claim 8, wherein receiving the message generation trigger signal is in response to the payment card transaction performed by the targeted cardholder.

10. The method of claim 7, wherein the message generation trigger signal includes an indication of a monitoring indicator, an indication of a monitoring time period, and an indication of a monitoring range, the method further comprising:

it is determined whether the monitoring score is within the monitoring range,

wherein extracting the targeted cardholder profile from the database comprises extracting the targeted cardholder profile if the monitoring score is determined to be within a predetermined range.

11. The method of claim 7, the message generation trigger including an indication of reward criteria for rewarding a cardholder, the method further comprising:

identifying a reward score associated with the reward criteria; and

determining whether the reward score satisfies the reward criteria,

wherein extracting the targeted cardholder profile from the database comprises extracting the targeted cardholder profile if it is determined that the reward score of the targeted cardholder profile meets the reward criteria.

12. The method of any of claims 7-11, wherein the message payload is in the form of a batch file that includes a plurality of custom messages and a plurality of indications of payment card identifiers associated with targeted cardholder profiles.

13. The method of any of claims 10 to 12, wherein in response to a scheduler receiving the message generation trigger signal, the method further comprises receiving the message generation trigger signal from the scheduler at each preset time period.

14. The method of claim 13, further comprising resetting the monitoring score when claim 13 is dependent on claim 10 or resetting the reward score when claim 13 is dependent on claim 11, at each of the preset time periods, according to the scheduler.

15. The method of claims 7 to 14, wherein the message generation trigger signal is received from an external request from an application interface (API).

16. The method of claims 7 to 15, wherein the step of updating the score comprises increasing the score according to the number of payment card transactions performed relative to an index associated with the score.

17. The method of claims 7 to 16, wherein the transaction attributes comprise at least one of: merchant attributes, transaction amount, and transaction nature.

18. The method of claims 7 to 17, further comprising receiving feedback associated with the custom message.

19. The method of claims 7-18, further comprising analyzing transaction data associated with a plurality of payment card transactions performed against the cardholder profile to derive derivative attributes using transaction attributes of the plurality of payment card transactions.

20. A non-transitory computer-readable medium having stored thereon program instructions for causing at least one processor to perform the method of any one of claims 7 to 19.