Payment device registration in linked promotion

Abstract

The present invention provides a dynamic graphical object managed by a financial institution that issues a payment device that prevents a third party from accessing sensitive account data when the payment device is linked to a marketing document provided by the third party. A payment processing server uses an alias for the sensitive data and configures the dynamic graphical object with the alias. The object may also include instructions that link the sensitive data to the alias and allow the payment processing server to monitor transactions with the third party. The payment processing server can then mediate communications between the consumer and the third party without exposing the sensitive data.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of priority to U.S. Application Serial No. 15 / 041,917, filed on February 11, 2016, entitled “PAYMENT DEVICE ENROLLMENT IN LINKED OFFERS,” the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to methods and systems for automatically linking promotions and coupons to a payment device. Background Art

[0004] The background description provided herein is for the purpose of generally presenting the context of the present disclosure. To the extent described in this background section, the work of the presently named inventors and various aspects described that may not otherwise be prior art at the time of filing are neither explicitly nor implicitly admitted as prior art to the present disclosure.

[0005] Promotions, discounts, and other forms of marketing documents that implement marketing programs to provide consumers with benefits in exchange for purchasing specific products or services, or other benefits set in exchange, can be linked to a payment device such as a credit card. In current payment device systems, the process of linking a marketing document to a payment device requires a primary account number ("PAN") for the payment device. In addition, the third party that provides the marketing document to the PAN owner (i.e., the marketing document issuer, not the PAN owner, nor the financial institution that issued the PAN to the owner) is responsible for collecting the PAN to complete the linking process. The sharing and collection of PANs by third parties poses security and privacy risks to both the PAN owner and the issuing financial institution. There is an increasing need for methods of linking PANs to marketing documents without exposing the PAN owner and the issuing financial institution to this risk. Summary of the invention

[0006] The features and advantages described in the present invention and the following specific embodiments are not all-inclusive. Many additional features and advantages will be apparent to those of ordinary skill in the art based on the accompanying drawings, descriptions, and claims. In addition, other embodiments may omit one or more (or all) of the features and advantages described in the present invention.

[0007] Computer-implemented systems and methods may provide solutions to the security risks described above. In some embodiments, the solution may include a graphical object that is managed by the issuing financial institution and presented with a marketing document. The payment processing server may be configured to create a dynamic graphical object and send the object to the user's computing device in response to a request for display on the user's computing device. The dynamic graphical object may be configured by the payment processing server using information or an alias of information from the issuing financial institution (e.g., the user's PAN and other information). The object may also include instructions to link the PAN to an alias for the user, such as an email address, phone number, computing device, or other identifying information known by a third party that does not pose a security risk. In some embodiments, the dynamic graphical object may also include a graphical image of the user's payment device, including the PAN, so that the user can easily identify the payment device linked to the marketing document.

[0008] In some embodiments, the payment device and marketing agreement linking system may include a payment processing server and a marketing document server. The payment processing server may configure a dynamic button object using at least an alias for consumer account data and marketing document data. The consumer account data may correspond to a payment device. The marketing document server may send the marketing document data for the dynamic button object to a consumer computing device via a computer network. In response to receiving a request from a consumer computing device, the payment processing server links the alias to the marketing document data sent to the consumer computing device.

[0009] In another embodiment, a computer-implemented method may link a payment device to marketing document data. The method may configure a dynamic button object at a payment processing server. The dynamic button object includes an alias and indicates marketing document data. The alias may correspond to a payment device, and consumer account data is communicatively coupled to the payment processing server. In response to a first request from a consumer computing device, the method may send the dynamic button object from the payment processing server to the consumer computing device via a computer network. In response to a second request from the consumer computing device, the method may send the indicated marketing document data to the consumer computing device. In response to a third request from the consumer computing device, the method may link the alias to the indicated marketing document data and the consumer computing device. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 illustrates a system for registering and linking a payment device to marketing documents, promotions and other information or dynamic objects;

[0011] Figure 2Aillustrates a first view of an exemplary payment device in a system for registering and linking a payment device to marketing documents, promotions, and other information or dynamic objects;

[0012] Figure 2B a second view illustrating an exemplary payment device in a system for registering and linking a payment device to marketing documents, promotions, and other information or dynamic objects;

[0013] Figure 3 Diagram for use Figure 1 system registration and process flows for linking payment devices to marketing documents, promotions and other information or dynamic objects; and

[0014] Figure 4 The diagram illustrates a computing device used in a system for registering and linking a payment device to marketing documents, promotions, and other information or dynamic objects, and implementing the various process flows or methods described herein.

[0015] For purposes of illustration only, the drawings depict preferred embodiments. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods shown herein may be employed without departing from the principles described herein. DETAILED DESCRIPTION

[0016] Figure 1 Generally illustrated is one embodiment of a system 100 for registering and linking payment devices to marketing documents, promotions, and other information and dynamic objects as described herein. The system 100 may include a front-end component 102 (e.g., a user or consumer computing device 103, such as a smart phone, personal computer, tablet, etc.) and a back-end component 104 (e.g., a payment processing system 106 and a marketing document system 108). The front-end component 102 and the back-end component 104 may communicate with each other via a network 110 (e.g., a computer network, an Internet connection, etc.). The system 100 may include various software or computer-executable instructions and unique hardware components or modules that may use the software and instructions to manage registration and linking payment devices to marketing documents, promotions, and other information and dynamic objects as described herein. Each module may be implemented as a computer-readable memory containing computer-readable instructions (i.e., software) that is executed by a processor of the system 100 within a dedicated or unique computing device. These modules may perform various tasks associated with registering and linking payment devices to marketing documents, promotions, and other information and dynamic objects as described herein. The system 100 may also include hardware and software applications and various data communication channels for communicating data between various dedicated or unique front-end 102 and back-end 104 hardware and software components.

[0017] The payment processing system 106 may include one or more instruction modules, including a dynamic object module 112, which may generally include instructions for causing a processor 114 of a payment processing server 116 to functionally communicate with a plurality of other computer executable steps or modules, including a graphic object module 112A and a token module 112B. The dynamic object module 112 and modules 112A and 112B may include instructions that, once loaded into the server memory 113, when executed by one or more computer processors 114, register and transfer payment devices 200 ( Figure 2A and 2B ) links to marketing documents, promotions and other information and dynamic objects of the marketing document system 108.

[0018] The data warehouse 117 may include account data 117A, which includes various pieces of data describing the account of the payment device owner and the user of the payment processing system 106. This account data 117A may be embodied in the payment device 200 as described herein. Figure 2A and Figure 2B , the payment device 200 can take a variety of shapes and forms. In some embodiments, the payment device 200 is a traditional card, such as a debit card or a credit card. In other embodiments, the card can be a key fob on a key chain. As long as the payment device 200 can communicate securely with the payment acceptance device, the form of the payment device may not be particularly critical and can be selected in design. For example, many traditional payment devices 200 may have to be read by a magnetic stripe reader, and therefore the size of the payment device 200 may have to fit the magnetic card reader. In other instances, the payment device 200 can communicate via near field communication, and the form of the payment device 200 can be almost any form. Of course, other forms are also possible based on the purpose of the card, the type of reader being used, etc.

[0019] Physically, the payment device 200 may be a card, and the card may have multiple layers to contain various elements that make up the payment device 200. In one embodiment, the payment device 200 may have a substantially flat front surface 202 and a substantially flat rear surface 204 opposite the front surface 202. Logically, in some embodiments, the surfaces 202, 204 may have some embossments 206 including a primary account number ("PAN") 206A and a card verification number ("CVN") 206B.

[0020] return Figure 1, the checkout module 118 may include various instructions that, once executed by the processor 114, facilitate the user's use of the payment device 200 for financial transactions and link promotions and coupons to the payment device 200 without exposing sensitive data (e.g., the user's PAN) to third parties that provide promotions and coupons. The checkout module 118 may include instructions that, once loaded into the server memory 113 and executed by one or more computer processors 114, enable the user to complete payment using the payment device 200 and its corresponding account data 117A using, for example, the PAN 206A and other data, and also cooperate with the dynamic object module 112 and the marketing document system 108 to facilitate registration and link the payment device 200 to marketing documents, promotions and other information and dynamic objects as described herein. In some embodiments, the checkout module 118 may include instructions for processing payments in online financial transactions between the consumer computing device 103 and the online merchant. For example, the checkout module 118 may include instructions that cause the account data 117A corresponding to the consumer initiating the transaction to be accessed through the network 110 to approve or deny the payment amount to the merchant. The checkout module 118 may also call one or more APIs of the dynamic object module 112 to register the user in a promotion or other offer managed by the marketing document system 108 .

[0021] The checkout module may also include instructions that coordinate the execution of instructions by the dynamic object module 112 to configure the dynamic button object 120. For example, the graphic object module 112A may include instructions that cause an application executing on the consumer computing device 103 to display the dynamic button object 120 within a graphical user interface ("GUI") 122 of the consumer computing device 103. In some embodiments, the GUI 122 may include a browser or other application stored in a memory 123 of the consumer computing device 103 and executed on a processor 124 that displays the dynamic button object 120. The dynamic button object 120 may include several elements, including a token 120A and a marketing document graphic object 120B as described herein.

[0022] The token module 112B may include instructions that cause a set of instructions or tokens to be created to link data (e.g., promotions, coupons, etc.) from the marketing document system 108 to the payment device 200 and its corresponding account data 117A. In some embodiments, a set of instructions may be created by the token module 112B. This set of instructions may include what is commonly referred to as a cookie (data stored on the user's local terminal).

[0023] Cookies are small pieces of text stored by GUI 122 on consumer computing device 103. A cookie consists of one or more name-value pairs containing bits of information. When a user requests information from a web server, the name portion and value portion of the cookie may be set by the server receiving the web request. The value portion is a random value that allows identification of the requester.

[0024] In some embodiments, when a user selects a dynamic button object 120 within the GUI 122, the GUI 122 executes instructions associated with the dynamic button object 120 to request information from the backend component 104 and facilitate the linking process described herein. For example, the GUI 122 may execute instructions to request information from the payment processing server 116, which may also request information from the marketing document server 128. In other embodiments, the GUI 122 executes instructions to request marketing document data 127A directly from the marketing document server 128. In some embodiments, the marketing document data 127A includes an ad unit or offer wall object for display within the GUI 122. The payment processing server 116 or the marketing document server 128 may then set the name portion of the token 120A to the corresponding server name and the value portion of the token 120A to a value that identifies the user of the consumer computing device 103 corresponding to the record of the account data 117A. In some embodiments, this value may be a random number, an email address, a device identifier, or other data that is an alias for the user. This value may then be stored by the payment processing service system 106 or the marketing document system 108 to identify the user. Importantly, this value and name may then be used by the payment processing service 116 to act as a mediator between the account data 117A and the marketing document data 127A, so that the consumer can view and select various promotions without handing over security-sensitive data such as their PAN. In some embodiments, the payment processing system 106 generally may include, and the checkout module specifically may include, instructions to monitor transactions from a consumer computing device to a merchant associated with the marketing document data 127A. In response to a user selection of the dynamic button object 120, the marketing data may be sent to the consumer computing device 103 in the transaction. The payment processing system 106 may then execute the instructions to apply any discounts or credits described by the marketing document data 127A to the monitored transactions. The payment processing system 106 may also authenticate the consumer as the owner of the specific payment device 200 used in the transaction.

[0025] The graphic object module 112A of the dynamic object module 112 may associate a marketing document graphic object 120B with a dynamic button object 120 displayed within the GUI 122 that represents marketing document data 127A and / or account data 117A. For example, the marketing document graphic object 120B may include text or an image describing a particular promotion, coupon, or other offer, and once the consumer selects the marketing document graphic object 120B, the account data 117A is linked to the particular marketing document data 127A. The marketing document graphic object 120B may also include a graphical element. For example, the graphical element may include an image of the consumer's payment device 200, which the consumer may use to associate the device 200 with the account data 117A corresponding to the marketing document data 127A.

[0026] The marketing document system 108 may also include a marketing document server 128 including a memory 133 and a processor 134. The marketing document module 140 may include instructions that, when executed by the processor 134, cause the marketing document system 108 to send the marketing document data 127A or an indication of the marketing document data 127A (e.g., a link to a web file for the marketing document data 127A, an embodiment of the data, etc.) to the consumer computing device 103 via the network 110. For example, the marketing document module 140 may include a marketing document application programming interface (“API”) 140A that includes instructions to facilitate linking the payment device 200 to the marketing document data 127A by communicating with the payment processing server 116 without exposing sensitive information (e.g., the consumer's PAN) to a third party. In some embodiments, the API 140A includes instructions that, in response to selecting a dynamic button object 120 within the GUI 122 of the consumer computing device 103, cause the marketing document system 108 to send the ad unit or other marketing document data 127A to the consumer computing device 103. The marketing document system 108 may send the marketing document data 127A to the consumer computing device 103 via the payment processing system, which in turn sends the marketing document data 127A to the consumer computing device 103 .

[0027] Reference Figure 3 , system 100, generally processors 114, 124, 134 of payment processing server 116, consumer computing device 103, and / or marketing document server 128, respectively, described herein, may execute method 300 to link promotions, coupons, and other marketing document data 127A to payment device 200 without exposing sensitive account information to third parties managing marketing document data 127A. Each of the various "steps" described herein may correspond to one or more computer-executable instructions executed by modules of system 100 on one or more processors, such as processors 114, 124, and 134.

[0028] At step 302, method 300 may cause one or more processors to execute instructions to create a dynamic button object 120. In some embodiments, step 302 may include instructions to associate a token 120A and a marketing document graphical object 120B with the dynamic button object 120. As described above, token 120A may include a cookie or other text or instructions that allows an alias to be associated with the consumer's account data 116A.

[0029] At step 304, method 300 may cause one or more processors to execute instructions to start a checkout process. For example, in response to a first request from consumer computing device 103, payment processing system 106 may cause GUI 122 of consumer computing device 103 to display one or more graphical objects indicating payment options using payment device 200, and send dynamic button object 120 to the consumer computing device to display at least a graphical portion of the object during the checkout process. For example, a "VisaCheckout" icon may indicate a payment option using the same The graphical portion of the dynamic button object 120 may display an image of the payment device corresponding to the consumer and an indication of the availability of the marketing document data corresponding to the promoted transaction or the marketing document data itself.

[0030] At step 305, if the consumer selects the dynamic button object 120 at the consumer computing device 103, then at step 306, the method 300 may cause one or more processors to execute instructions to send and receive dynamic button object selections. In some embodiments, the consumer computing device 103 may execute instructions to send a second request, message, or instruction to the payment processing server 116, which in turn calls the marketing document server 128. The marketing document data 127A may then be sent to the consumer computing device 103 via the network 110 for display within the GUI 122 of the consumer computing device 103. Thus, the payment processing system 106 may mediate communications between the consumer and the marketing document system 108 without exposing PAN or other sensitive data to third parties. Otherwise, at step 305, if the consumer does not select the dynamic button object 120 at the consumer computing device 103, the method 300 may continue to step 312, which is described below.

[0031] At step 308, method 300 may cause one or more processors to execute instructions that call marketing document API 140A. In some embodiments, API 140A may execute instructions that facilitate a registration process for consumer computing device 103. For example, step 308 may cause a registration form or other interface to be displayed within GUI 122. The form may allow the consumer to enter an alias or other information to facilitate a linking process as described herein.

[0032] At step 310, if the payment processing server 116 does not receive a third request, message, or instruction from the consumer computing device 103 to complete the registration process, then at step 312, the consumer can complete the transaction without linking sensitive information of the payment device 200 to the marketing profile data 127A. Completing the transaction may cause the payment processing system 106 to execute instructions to apply any discounts or credits described by the marketing profile data 127A to the monitored transaction. The payment processing system 106 may also authenticate the consumer as the owner of the specific payment device 200 used in the transaction.

[0033] At step 310, if the payment processing server 116 receives a third request, message, or instruction from the consumer computing device 103 to complete the registration process, the method 300 may proceed to step 314 to link the alias or other non-sensitive portion of the dynamic button object 120 (e.g., the token 120A) to the payment device 200 without exposing any sensitive data (e.g., the consumer's PAN) to the marketing document system 108. At step 316, the method 300 may cause the one or more processors to execute instructions to complete the transaction initiated by the consumer computing device 103, and at step 318, to execute instructions to monitor any future transactions between the consumer computing devices 103 and / or transactions that include the account data 117A of the transaction completed at step 316. As described above with respect to step 312, completing the transaction may include executing instructions to apply any discounts or credits described by the marketing document data 127A to the monitored transaction, and authenticating the consumer as the owner of the particular payment device 200 used in the transaction. Monitoring user transactions at step 318 may generally include, in response to user selection of the dynamic button object 120 , causing the one or more processors to monitor transactions of the consumer computing device with a merchant associated with the marketing document data 127A sent to the consumer computing device 103 .

[0034] After executing the instructions associated with step 312 or 318, the method 300 may end. Thus, the method 300 may cause the processors 114, 124, 134 of the payment processing server 116, the consumer computing device 103, and the marketing document server 128 to execute instructions to manage registration and linking payment devices to marketing documents, promotions, and other information and dynamic objects as described herein.

[0035] Figure 4 is a high-level block diagram of an exemplary computing system 400 for use with the systems and methods for registering and linking payment devices to marketing documents, promotions, and other information and dynamic objects as described herein. Computing device 401 may include a server (e.g., payment processing server 116, marketing document server 128, etc.), a mobile computing device (e.g., consumer computing device 103, a smart phone, a tablet computer, a Wi-Fi enabled device, or other personal computing device capable of wireless or wired communications), a thin client, or other known types of computing devices. Those skilled in the art will recognize that other types of computing devices with different architectures may be used based on the disclosure and teachings herein. The exemplary systems and methods for registering and linking payment devices to marketing documents, promotions, and other information and dynamic objects may be implemented and executed using a processor system similar or the same as the exemplary systems and methods for registering and linking payment devices to marketing documents, promotions, and other information and dynamic objects. Figure 1 Although the exemplary system 400 is described below as including a plurality of peripherals, interfaces, chips, memories, etc., one or more of these elements may be omitted from other exemplary processor systems for implementing and executing the exemplary system for registering and linking payment devices to marketing documents, promotions and other information and dynamic objects. In addition, other components may be added.

[0036] like Figure 4 As shown, computing device 401 includes a processor 402 coupled to an interconnect bus. Processor 402 includes a register file or register space 404, which is Figure 4 402 is shown as being entirely on-chip, but it may alternatively be entirely or partially off-chip and directly coupled to processor 402 via dedicated electrical connections and / or via an interconnect bus. Processor 402 may be any suitable processor, processing unit, or microprocessor. Figure 4 Although not shown, computing device 401 may be a multi-processor device and, therefore, may include one or more additional processors that are the same as or similar to processor 402 and that are communicatively coupled to the interconnection bus.

[0037] Figure 4The processor 402 is coupled to a chipset 406, which includes a memory controller 408 and a peripheral input / output (I / O) controller 410. As is well known, a chipset typically provides I / O and memory management functions, as well as a plurality of general and / or special registers, timers, etc. that can be accessed or used by one or more processors coupled to the chipset 406. The memory controller 408 performs the function of enabling the processor 402 (or multiple processors if there are multiple processors) to access system memory 412 and mass storage 414, which may include either or both of a memory cache (e.g., a cache within the memory 412) or a disk cache (e.g., a cache within the mass storage 414).

[0038] System memory 412 may include any desired type of volatile and / or non-volatile memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, read-only memory (ROM), etc. Mass storage 414 may include any desired type of mass storage device. For example, if computing device 401 is used to execute module 416 (e.g., various modules and other modules for registering and linking payment devices to marketing documents, promotions and other information and dynamic objects as described herein). Mass storage 414 may include a hard drive, an optical drive, a tape storage device, a solid-state memory (e.g., flash memory, RAM memory, etc.), a magnetic memory (e.g., a hard drive), or any other memory suitable for mass storage. As used herein, the terms module, box, function, operation, process, routine, step, and method refer to tangible computer program logic or tangible computer executable instructions that provide specified functions for computing device 401 and system 100. Therefore, modules, boxes, functions, operations, processes, routines, steps, and methods can be implemented in hardware, firmware, and / or software. In one embodiment, program modules and routines are stored in mass storage 414, loaded into system memory 412 and executed by processor 402, or may be provided from a computer program product stored in a tangible computer-readable storage medium (e.g., RAM, hard disk, optical / magnetic media, etc.).

[0039] The peripheral I / O controller 410 performs functions that enable the processor 402 to communicate with the peripheral input / output (I / O) device 424, the network interface 426, and the local network transceiver 428 via the peripheral I / O bus (via the network interface 426). The I / O device 424 can be any desired type of I / O device, such as a keyboard, a display (e.g., a liquid crystal display (LCD), a cathode ray tube (CRT) display, etc.), a navigation device (e.g., a mouse, a trackball, a capacitive touch pad, a joystick, etc.), etc. The I / O device 424 can be used together with the module 416, etc. to receive data from the transceiver 428, send data to the back-end components of the system 100, and perform any operation involving the methods described herein. The local network transceiver 428 can include support for Wi-Fi networks, Bluetooth, infrared, or other wireless data transmission protocols. In other embodiments, an element can simultaneously support each of the various wireless protocols used by the computing device 401. For example, a software radio can be able to support multiple protocols via downloadable instructions. In operation, computing device 401 may be able to periodically poll visible wireless network transmitters (both cellular and local networks) on a periodic basis. Such polling may be possible even when computing device 401 supports normal wireless traffic. Network interface 426 may be, for example, an Ethernet device, an asynchronous transfer mode (ATM) device, an 802.11 wireless interface device, a DSL modem, a cable modem, a cellular modem, etc. that enables system 100 to communicate with another computer system having at least the elements described with respect to system 100.

[0040] Although the memory controller 408 and the I / O controller 410 Figure 4 406, but the functions performed by these blocks may be integrated into a single integrated circuit, or may be implemented using two or more separate integrated circuits. The computing system 400 may also implement module 416 on a remote computing device 430. The remote computing device 430 may communicate with the computing device 401 over an Ethernet link 432. In some embodiments, the module 416 may be retrieved from a cloud computing server 434 via the Internet 436 by the computing device 401. When a cloud computing server 434 is used, the retrieved module 416 may be programmatically linked to the computing device 401. The module 416 may be a collection of various software platforms, including artificial intelligence software and document creation software, or may be a collection of modules 416 residing in a computing device 401 or a remote computing device 430. Executed in a virtual machine (JVM) environment Modeling module 420 and execution module 422 may also be "plug-ins" adapted to execute in a web browser located on computing devices 401 and 430. In some embodiments, module 416 may communicate with back-end components 438 such as via the Internet 436. Figure 1 The back-end component 104 communicates with the back-end component 104.

[0041] System 400 may include, but is not limited to, any combination of LAN, MAN, WAN, mobile network, wired network or wireless network, private network or virtual private network. In addition, although for simplicity and clarity of description, Figure 4 Only one remote computing device 430 is shown, but it should be understood that many client computers are supported and can communicate in system 400.

[0042] In addition, some embodiments are described herein as including logic or a number of components, modules or mechanisms. A module may constitute a software module (e.g., a code or instruction embodied on a machine-readable medium or embodied in a transmission signal, wherein the code is executed by a processor) or a hardware module. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in some manner. In an example embodiment, one or more computer systems (e.g., independent client or server computer systems) or one or more hardware modules of a computer system (e.g., a processor or a group of processors) may be configured as a hardware module by software (e.g., an application or application portion), and the hardware module operates to perform certain operations as described herein.

[0043] In various embodiments, hardware modules can be implemented mechanically or electronically. For example, a hardware module may include dedicated circuits or logic that are permanently configured (e.g., a dedicated processor, such as a field programmable gate array (FPGA)) or an application specific integrated circuit (ASIC) to perform certain operations. A hardware module may also include programmable logic or circuits (e.g., included in a general purpose processor or other programmable processor) that are temporarily configured by software to perform certain operations. It is recognized that the decision to implement a hardware module mechanically, in a dedicated and permanently configured circuit or in a temporarily configured circuit may be determined by cost and time factors.

[0044] Therefore, the term "hardware module" should be understood to include a tangible entity, as long as the entity is physically constructed, permanently configured (e.g., hardwired) or temporarily configured (e.g., programmed) to operate in a certain manner or perform certain operations as described herein. As used herein, "hardware-implemented module" refers to a hardware module. Considering an embodiment in which the hardware module is temporarily configured (e.g., programmed), it is not necessary to configure or initialize each hardware module at any one time. For example, when the hardware module includes a general-purpose processor configured using software, the general-purpose processor can be configured into corresponding different hardware modules at different times. The software can configure the processor accordingly, for example, to constitute a specific hardware module at one time and to constitute a different hardware module at a different time.

[0045] Hardware modules can provide information to other hardware modules and receive information from other hardware modules. Therefore, the described hardware modules can be considered to be communication coupled. When multiple such hardware modules exist simultaneously, communication can be realized by the signal transmission (e.g., by suitable circuits and buses) connecting the hardware modules. In the embodiment where multiple hardware modules are configured or initialized at different times, the communication between these hardware modules can be realized by, for example, storing and retrieving information in a memory structure accessible to multiple hardware modules. For example, a hardware module can perform an operation, and the output of the operation is stored in a memory device coupled to its communication. Another hardware module can then access the memory device to retrieve and process the output of the storage at a later time. The hardware module can also initiate communication with an input or output device, and can operate resources (e.g., a collection of information).

[0046] The various operations of the example methods described herein may be performed, at least in part, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, these processors may constitute processor-implemented modules that operate to perform one or more operations or functions. The modules referred to herein include processor-implemented modules in some example embodiments.

[0047] Similarly, the methods or routines described herein may be implemented by processors at least in part. For example, at least some operations of the method may be performed by a processor or a processor-based hardware module. The execution of certain operations may be distributed on one or more processors that not only reside in a single machine but are deployed on many machines. In some example embodiments, one or more processors may be located in a single location (e.g., in a home environment, an office environment, or as a server farm), while in other embodiments, the processors may be distributed in many locations.

[0048] The one or more processors may also be operable to support execution of related operations in a "cloud computing" environment or as "software as a service" (SaaS). For example, at least some operations may be performed by a group of computers (as instances of machines including the processors), which may be accessed via a network (e.g., the Internet) and through one or more appropriate interfaces (e.g., application programming interfaces (APIs)).

[0049] The execution of certain operations may be distributed across one or more processors that reside not only within a single machine but are deployed across many machines. In some example embodiments, one or more processors or processor-implemented modules may be located at a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other example embodiments, one or more processors or processor-implemented modules may be distributed across many geographic locations.

[0050] Some parts of this specification are presented in accordance with algorithms or symbolic representations of operations on data stored in machine memory (e.g., computer memory) as bits or binary digital signals. These algorithms or symbolic representations are examples of techniques used by ordinary technicians in the field of data processing to convey the essence of their work to other technicians in the field. As used herein, an "algorithm" is a self-consistent sequence of operations or similar processes that lead to a desired result. In this context, algorithms and operations involve the physical manipulation of physical quantities. Usually, but not necessarily, such quantities can take the form of electrical, magnetic or optical signals that can be stored, accessed, transmitted, combined, compared or otherwise manipulated by a machine. Sometimes, mainly for reasons of common usage, it is convenient to refer to these signals using words such as "data", "content", "bit", "value", "element", "symbol", "character", "condition", "number", "digital", etc. However, these words are just convenient labels, associated with appropriate physical quantities.

[0051] Unless specifically noted otherwise, discussions herein using words such as "process," "compute," "calculate," "determine," "present," "display," etc. may refer to the actions or processes of a machine (e.g., a computer) that manipulates or transforms data represented as physical (e.g., electrical, magnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.

[0052] As used herein, any reference to "some embodiments" or "embodiments" or "teachings" means that a particular element, feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. The phrases "in some embodiments" or "teachings" appearing in different places in this specification do not necessarily all refer to the same embodiment.

[0053] Some embodiments may be described using the expressions "coupled" and "connected" and their derivatives. For example, some embodiments may be described using the term "coupled" to indicate that two or more elements are in direct physical or electrical contact. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other. The embodiments are not limited in this context.

[0054] Furthermore, the drawings depict preferred embodiments for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods shown herein may be employed without departing from the principles described herein.

[0055] After reading this disclosure, those skilled in the art will understand additional alternative structural designs and functional designs of the systems and methods described herein through the principles disclosed herein. Therefore, although specific embodiments and applications have been illustrated and described, it should be understood that the disclosed embodiments are not limited to the precise constructions and components disclosed herein. Various modifications, changes and variations can be made to the arrangement, operation and details of the systems and methods disclosed herein without departing from the spirit and scope defined by any of the appended claims, which will be apparent to those skilled in the art.

Claims

1. A system for connecting a payment device to marketing document data provided by a third-party server, comprising: A payment processing server comprising a processor and a memory storing instructions executable by the processor to: storing consumer account data on a payment device, the consumer account data including a primary account number and a consumer alias; Setting the value portion of the token to the consumer alias; setting the alias portion of the token to a server name for the payment processing server; connecting the token to a dynamic button object, the dynamic button object indicating marketing document data; In response to selection of the dynamic button object: receiving a value portion of the token; linking the consumer account data to the marketing document data based on a value portion of the token; as well as The marketing document server is caused to provide the marketing document data so as to send the marketing document data to a consumer computing device corresponding to the consumer account data without exposing the primary account to the marketing document server.

2. The system of claim 1, further comprising instructions executable by the processor to link a graphical object with the dynamic button object, the graphical object comprising an image for the marketing document data.

3. The system according to claim 2, wherein: The graphical object also includes an image of the payment device.

4. The system according to claim 3, wherein: The instructions to set the value portion of the token to the consumer alias include instructions to send the dynamic button object to the consumer computing device corresponding to the consumer account data in response to receiving a request from the consumer computing device.

5. The system according to claim 4, wherein: The consumer alias includes one or more of a random number, an email address, and a device identifier for the consumer computing device.

6. The system according to claim 5, wherein: The marketing document data includes one or more of an ad unit or an offer wall object for display within a GUI of the consumer computing device.

7. The system according to claim 6, wherein: The memory includes further instructions to monitor a transaction from the consumer computing device, the transaction including a value portion of the token and the marketing document data.

8. The system according to claim 7, wherein: The memory includes further instructions to apply one or more of a discount or credit described by the marketing document data to the transaction.

9. The system according to claim 8, wherein: The memory includes further instructions for authenticating a consumer as an owner of the consumer computing device used to complete the transaction.

10. A computer-implemented method for linking a payment device to marketing document data provided by a third-party server, the method comprising: storing consumer account data on a payment device, the consumer account data including a primary account number and a consumer alias; Setting the value portion of the token to the consumer alias; setting the alias portion of the token to a server name for a payment processing server; connecting the token to a dynamic button object, the dynamic button object indicating marketing document data; In response to selecting a graphic object within the dynamic button object: receiving a value portion of the token; concatenating the consumer account data to the marketing document data based on a value portion of the token; as well as The marketing document server is caused to provide the marketing document data so as to send the marketing document data to a consumer computing device corresponding to the consumer account data without exposing the primary account to the marketing document server.

11. The computer-implemented method of claim 10, further comprising linking a graphical object with the dynamic button object, the graphical object comprising an image for the marketing document data.

12. The computer-implemented method of claim 11, wherein: The graphical object also includes an image of the payment device.

13. The computer-implemented method of claim 12, wherein: The marketing document data includes one or more of an ad unit or an offer wall object for display within a GUI of the consumer computing device.

14. The computer-implemented method of claim 13, further comprising monitoring transactions conducted using the consumer alias of the consumer computing device, the transactions comprising the value portion of the token and the marketing document data.

15. The computer-implemented method of claim 14, further comprising applying one or more of a discount or a credit described by the marketing document to the transaction.

16. The computer-implemented method of claim 15, further comprising authenticating a consumer as an owner of the consumer computing device used to complete the transaction.

17. The computer-implemented method of claim 16, further comprising blocking access to a primary account corresponding to the consumer account data using the dynamic button object.

Images