System and method for communicating with an electronic device

Abstract

The disclosed systems and methods provide a display based on a representation of an electronic transaction account, and the display can display information about the electronic transaction account or other data that a consumer desires to be displayed.

Description

Background Art

[0001] Consumers often have multiple e-commerce accounts. Each e-commerce account often offers rewards or rebates when used. Furthermore, rewards may vary based on various factors, such as, but not limited to, purchase type, month of year, and amount spent. Trying to remember which e-commerce account offers which offer can be challenging because the e-commerce account number is typically not noted on the physical card or on the e-commerce account's display on an electronic device. Summary of the Invention

[0002] The disclosed systems and methods provide a display based on a representation of an electronic transaction account, and the display can display information about the electronic transaction account or other data desired by a consumer. In one embodiment, a method for displaying a graphical object on a payment device can be disclosed. A processor of a mobile computing device can receive a graphical object corresponding to a payment device, wherein the graphical object is created by the owner or responsible party of the payment device. The graphical object can be reviewed to determine whether it conforms to expected formats and protocols. If the graphical object conforms to the expected protocols, the processor of the mobile computing device can display the graphical object in a display area. BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Figure 1 A sample electronic payment system is shown;

[0004] Figure 2 shows a sample flow of computational blocks that may be performed by the system;

[0005] Figure 3 A sample payment device having a display is shown;

[0006] Figure 4 A sample smartphone is shown as a payment device with a display;

[0007] Figure 5 showing a payment device in communication with a network; and

[0008] Figure 6 Sample computing elements that make up a payment device are shown.

[0009] Those skilled in the art will appreciate that the elements in the figures are shown for simplicity and clarity, and therefore not all connections and options are shown to avoid obscuring various aspects of the present invention. For example, common but well-understood elements that are useful or necessary in commercially viable embodiments are generally not depicted to facilitate unimpeded viewing of the various embodiments of the present disclosure. It will be further understood that certain actions and / or steps may be described or depicted in a particular order of occurrence, but those skilled in the art will understand that such specificity regarding order is not actually required. It will also be understood that the terms and expressions used herein are defined relative to their corresponding queries and research areas, unless a specific meaning has been otherwise set forth herein. DETAILED DESCRIPTION

[0010] The present disclosure will now be described more fully with reference to the accompanying drawings, which form a part of the present disclosure and illustrate specific exemplary embodiments by way of illustration, by which the present disclosure may be practiced. The presentation of these diagrams and exemplary embodiments should be understood as an example, and is not intended to be limited to any one of the embodiments shown. The present disclosure may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein; in fact, these embodiments are provided to make the present disclosure thorough and complete, and will fully convey the scope of the present disclosure to those skilled in the art. In addition, the present disclosure may be embodied as a method or apparatus. Therefore, the present disclosure may take the form of a fully hardware embodiment, a fully software embodiment, or an embodiment combining software and hardware aspects. Therefore, the following detailed description should not be taken in a limiting sense.

[0011] System 100 may include a computer network 102 linking one or more systems and computer components. In some embodiments, system 100 includes a user computing device 104, a merchant computer system 106, a payment network system 108, and a transaction analysis system 110.

[0012] The network 102 may be variously described as a communication link, a computer network, an Internet connection, etc. The system 100 may include various software or computer-executable instructions or components stored on tangible memory and dedicated hardware components or modules that employ the software and instructions in actual applications to manage network nodes for transactions, as described herein.

[0013] The various modules may be implemented as computer-readable storage devices containing computer-readable instructions (i.e., software) for execution by one or more processors of the system 100 within a dedicated or unique computing device. The modules may perform various tasks, steps, methods, blocks, etc., as described herein. The system 100 may also include both hardware and software applications, as well as various data communication channels for transmitting data between the various dedicated and unique hardware and software components.

[0014] It is generally believed that a network includes the interconnection and interoperability of hardware, data and other entities. A computer network or data network is a digital telecommunications network that allows nodes to share resources. In a computer network, computing devices use connections between nodes, such as data links, to exchange data with each other. For example, a hardware network may include clients, servers, and intermediate nodes (e.g., user computer system 104, merchant computer system 106, payment network system 108, and transaction analysis system 110) in a graph topology. In a similar manner, a data network may include data nodes in a graph topology, wherein each node includes relevant or linked information, software methods, and other data. Nodes such as mobile computing devices 104 may be managed to facilitate transactions with other nodes of the system (e.g., merchant computer system) based on data and instructions from various other nodes of the system 100.

[0015] It should be noted that the term "server" as used throughout this application generally refers to a computer, other device, program or its combination, which includes a processor and memory to process and respond to the request of a remote user / node across a communication network. The server sends its information to the request "client". As used herein, the term "client" generally refers to a computer, program, other device, user and / or its combination that can process and issue a request and obtain and process any response from a server through a communication or data network. The computer, other device, related data set, program or its combination that promotes, processes information and requests, and / or promotes the transmission of information from a source user to a destination user is generally referred to as a "node". The network is generally considered to promote the transmission of information from the source point to the destination. The node specifically responsible for promoting the transmission of information from the information source to the destination is generally referred to as a "router". Networks have many forms, such as local area networks (LANs), Pico networks, wide area networks (WANs), wireless networks (WLANs) and the like. For example, the Internet is generally considered to be the interconnection of numerous networks, so that remote clients and servers can access and interact with each other.

[0016] Mobile computing device 104 may include a smartphone 104 or other computing device capable of sending and receiving wireless digital communications. The mobile computing device may include a processor 145, memory 146, and a battery. Mobile computing device 104 may include an RFID tag 104A or other device capable of transmitting a radio signal including mobile computing device data, such as battery charge. Memory 146 of mobile computing device 104 may include various modules that include instructions that, when executed by processor 145, generally control the functionality of mobile computing device 104 and, more specifically, integrate the mobile computing device into system 100. For example, some modules may include an operating system 150A, a browser module 150B, a communication module 150C, and a wallet module 150D. Communication module 150C may include processor-executable instructions for sending and / or receiving signals from contactless components of the system. In some embodiments, communication module 150C may include an RFID receiver or instructions for implementing an RFID receiver. Wallet module 150D may also include payment device data. The payment device data may securely identify the payment device and the user's payment account information to facilitate transactions between the mobile computing device 104 and the merchant computer system 106. In some embodiments, the payment device data may be tokenized so that only trusted partners can access the payment device data.

[0017] The merchant computer system 106 may include a computing device, such as a merchant server 129 including a processor 130 and a memory 132, the merchant server including components and instruction modules including processor-executable instructions to facilitate transactions with the mobile computing device 104 via other entities of the system 100. In some embodiments, the memory 132 may include a transaction communication module 134. The transaction communication module 134 may include instructions to send a merchant message 134A to other entities of the system 100 (i.e., 104, 108, 110) to generally indicate that a transaction has been initiated with the mobile computing device 104, and the wallet module 150D may include, among other things, payment account data, location data, and other data as described herein. For example, a node of the system 100 (e.g., mobile computing device 104 in general, and browser module 150B in particular) may access a merchant website to initiate a transaction. Some examples of transactions include the sale of tickets for specific seats at a venue.

[0018] The merchant computer system 106 may also include a transaction repository 142 and instructions for storing payment and other transaction data 142A in the transaction repository 142. The merchant computer system 106 may also include a product repository 143 and instructions for storing product and other data 143A in the product repository 143. In some embodiments, the merchant computer system 106 may also include instructions for sending payment device data corresponding to a payment device, transaction data 143A, and / or product data 143B, as well as other data received during a transaction, from the mobile computing device 104 to the payment network system.

[0019] The payment network system 108 may include a payment server 156, which includes a processor 158 and memory 160. Memory 160 may include a payment network module 162, which includes instructions for facilitating payments between parties (e.g., one or more users, merchants, etc.) using the system 100. Module 162 may be communicatively connected to an account holder data repository 164, which includes payment network account data 164A. Payment network account data 164A may include any data used to facilitate payments and other funds transfers between system entities (e.g., 104, 106, and 110). For example, payment network account data 164A may include identification data, account history data, payment device data, etc. Module 162 may also include instructions for sending payment messages 166 to other entities and components of the system 100 to complete transactions between the mobile computing system 104 and the merchant computer system 106. For example, module 162 may include instructions for sending a payment message 166 to transaction analysis system 110 or other entity of system 100 to complete a purchase transaction. Message 166 may include data authorizing the purchase transaction, such as an authorization number or other identification, and may be tokenized or encrypted by system 100 before message 166 is transmitted to the system entity via network 102.

[0020] Transaction analysis system 110 can be used to provide real-time or near real-time analysis of merchant risk scores. Server 116 can have a memory for storing computer-executable instructions, which can physically configure processor 118 according to the computer-executable instructions. Transaction table 112 can store individual transactions 112A, 112B, 112C, and 112D for periodic or real-time analysis. Transaction data can be stored in databases 112 and 124, which can contain past entries 122A and 124A that can be used to analyze current transaction risk.

[0021] Reference Figure 2, describes a processor-implemented method for displaying a graphical object 680 on a payment device 600. Graphical object 680 can take a variety of forms and shapes. Because graphical object 680 can be created by a user, graphical object 680 may be limited only by the user's imagination. It should be noted that in some embodiments, computer power, available memory, and available codecs and libraries may limit the number of graphical objects 680.

[0022] Some examples, but not limitations, of graphical object 680 include text, such as a description of an offer on payment device 600, a list of items to be purchased, a credit limit on an account, or an upcoming event that may require a purchase. Graphical object 680 may also be a graphic, such as an image of an item to be purchased, or a graphic used to remind the user of a card offer. In some embodiments, graphical object 680 may be a photo, animation, bitmap, drawing, video, or audio recording.

[0023] The payment device 600 may be in various forms. In one embodiment, for example, Figure 3 In the example, the payment device 600 may be a physical card. Figure 6 As shown, the physical card may include a power source 610, a processor 620, memory 630, an antenna 640, input / output circuitry 650, and a display 660. Power source 610 may be a battery, a capacitor, a solar cell, a wireless power source that can be activated when within range of a wireless power source, or a combination of these. Processor 620 may be a purpose-built processor designed to minimize power usage to conserve battery power. Furthermore, the graphics capabilities of processor 620 may be suitable for operation with display 660 in payment device 600, as display 660 may also be purpose-built.

[0024] As part of the physical payment card 600, namely, the display 660, which can be designed to meet the unique standards of the physical card 600, reference is again made to the display 660. In some embodiments, the display 660 can be flexible so that it does not break if the payment card 600 is bent. Furthermore, since the power supply 610 on the payment card 600 may have limited power, the display 660 can be designed to minimize power consumption. Furthermore, the size of the display 660 may be limited by the size of the physical card 600. Therefore, the number of pixels in the display 660 can be reduced while still providing sufficient clarity to effectively convey messages or images. An OLED display can be a sample display 660 that is flexible and has low power consumption. An electronic ink (E-ink) display 660 may also be suitable. Of course, other types of displays 660 are possible and contemplated.

[0025] In another embodiment, the payment device 600 may be capable of executing, for example, Figure 4The mobile computer device 600a of the mobile payment application is, for example, a smartphone. Some sample payment applications or wallet applications may include Visa Checkout, ApplePay, Google Pay, Masterpay, etc. The application may have an application programming interface (API) for obtaining the graphic 680a and displaying the graphic 680a as part of the payment application. Figure 6 As shown, similar to Figure 3 The mobile computing device of the card embodiment may have Figure 6 Shown are a power supply 610, a processor 620, a memory 630, an antenna 640, and input-output circuitry 650, along with a display 660. The processor 620 may also be designed to improve battery life and may be designed to improve the visibility of applications on the smaller display 660 of a mobile computing device or on a tablet computer 600a.

[0026] In e.g. Figure 5 In another embodiment shown, the portable payment device 600 can be in the form of a traditional credit card, and the credit card-shaped device 600 can communicate with a portable communication device 600a, such as a smartphone. In this way, the credit card-shaped device 600 can act as an NFC source to communicate with a nearby portable computing device 600a to receive a graphic.

[0027] In yet another embodiment, the portable payment device 600 may be close enough to the wireless access point 510 so that the card 600 or mobile computing device 600a can communicate with conventional wireless signals 510. If the appropriate login credentials are available and sufficiently secure, any form of payment device 600, 600a can communicate wirelessly over an available network to receive the graphical object 680.

[0028] refer to Figure 1 At block 210, the processor of the mobile computing device may receive a graphic object 680-680a corresponding to the payment device, where the graphic object 680-680a is created by a party responsible for the payment device 600-600a. The graphic object 680-680a may be text or may be as complex as a video or animation, depending on the capabilities of the payment device 600-600a.

[0029] Graphical objects 680 680a may be created by the account holder or an agent or account holder. Graphical objects 680 680a may be as simple as a text message, such as "Fuel consumption 5%." Another example may be that the account holder may transmit a note that reads "Attention - Balance as of 10 / 31 is $2,300."

[0030] In another example, a list may be transmitted as a graphical object 680 680a. The list may be a shopping list, such as "eggs, bacon, bread, milk." In yet another example, the list may be a reminder to buy something, such as "Ralph's birthday, Mom's anniversary, block party." In some embodiments, the display 660 660a is capable of displaying color, and the text in the graphical object 680 680a may be displayed in different colors, and the colors may have user-specific meanings.

[0031] In some other embodiments, a photo, animation, bitmap, jpeg picture, video can be a graphical object 680 680a. As previously mentioned, the graphical object 680 680a can be any object that can be displayed on the electronic display 660 660a driven by the processor 620.

[0032] Graphics 680 680a can be created in a variety of ways. In one embodiment, an application can be used to create graphics 680 680a. One possible application might be an electronic wallet application, which can allow for the creation of graphics 680 680a using a user interface designed for this purpose. A specific section of the application can be dedicated to creating graphics 680 680a, such as a word processor-style interface where text can be typed and other objects, such as images, animations, or videos, can be dragged and dropped or loaded into the display.

[0033] In another embodiment, graphics 680-680a can be extracted from another application. For example, a user can save a shopping list in a receipt application and extract the shopping list from the receipt application to transmit as graphics 680-680a. In the graphic creation user interface, the user can choose to use a file as graphics 680-680a or to connect with another application. As another example, a photo can be selected to be transmitted to the payment device as a reminder, and the photo can be displayed on the payment device 600-600a. In another embodiment, an application can push content to the payment application for display as graphics 680-680a. For example, and not by way of limitation, as the shopping list in the receipt application changes, the shopping list can be updated on the payment device display 660-660a.

[0034] In another example, graphics 680-680a may include both static elements and elements drawn from other applications. For example, and not by way of limitation, text may include phrases such as "Current Balance:," and blank space may contain references to separate programs or network locations. More specifically, a banking application may have an API set that can return balances in response to appropriate requests. The text may use the banking API to obtain and display the current balance on an electronic account represented by a payment account. Similarly, an API request for a calendar may display bills or upcoming events.

[0035] At block 220, a determination can be made as to whether the graphic 680 680a complies with acceptable protocols. Logically, the graphic 680 680a can be transmitted according to the protocol to improve efficiency and security. The payment device 600 600a may expect the graphic 680 680a to comply with the expected protocol. For example, and not by way of limitation, a fraudulent message may not comply with the protocol, and the system and method may recognize that the graphic 680 680a should be rejected. If the graphic 680 680a does not comply with the expected protocol, the payment device 600 600a may reject the graphic 680 680a at block 225. In some embodiments, a message indicating that the graphic 680 680a was rejected may be transmitted. By complying with the protocol, the communication may also include an element of security. For example, the graphic 680 680a may be transmitted using encryption, or the graphic may be sealed in an electronic token.

[0036] The sample protocol may include an application identifier that may identify the application used to create the graphics 680 680a, a graphic type identifier that may identify the type of graphics 680 680a, a size field that enables a receiver to understand the size of the message to be received, start data that indicates the beginning of the graphic data, and end data that may identify the end of the graphic data.

[0037] In some embodiments, an application programming interface (API) can be used to obtain graphics 680-680a. Graphics 680-680a can be stored remotely on a server and can be retrieved by transmitting a request signal to the remote server, and the server can respond with graphics 680-680a. In this way, graphics 680-680a can be continuously updated and should be updated when retrieved from the remote server.

[0038] If the graphic 680 680a conforms to the expected format, the method may continue at block 230. At block 230, the processor of the mobile computing device 600 600a may display the graphic object 680 680a in the display area 660 660a. In some embodiments, the payment device 600 600a may be able to render the data into an image 680 680a suitable for the display 660 660a. In another embodiment, the processing power of the payment device 600 600a may be limited and the rendering may be performed on a remote computing device, and the appropriate image 680 680a may be transmitted in a form that is computationally convenient for display on the display 660 660a.

[0039] The system and method can be triggered in various ways. In one embodiment, in response to a selection of a payment device 600 received within a threshold distance of a mobile computing device 600a executing a digital wallet application, a graphical object 680 can be displayed within a display 660 on a card-based payment device 600. For example, a user can place a smartphone 600a in a wallet and remove a traditional payment card 600 and place it near a payment terminal. The payment terminal can power the traditional payment card 600 either through the card 600 communicating with the payment terminal or through wireless power transmitted to the card 600, which can initiate the process.

[0040] In another embodiment, when the portable computing device 600a receives a selection of a payment account for the payment device 600a at a digital wallet application executed on the mobile computing device 600a, a graphical object 680 680a may be displayed on the card-based payment device 600 or the portable computing device 600a. Similarly, the user may take out the smartphone 600a, open the payment application, select a payment account, and the graphic 680a may be displayed on the payment application. Additionally, if the associated physical payment card 600 is nearby and powered, it may also display the graphic 680.

[0041] In some embodiments, graphics 680-680a may be specific to a payment account. In other embodiments, graphics 680-680a may be more general and applicable to all payment accounts. For example, graphics 680-680a containing a shopping list may be applicable to all payment accounts. However, graphics 680-680a indicating that a specific payment account offers a specific discount may only be displayed when a specific payment account is selected.

[0042] System 100 may include, but is not limited to, any combination of LAN, MAN, WAN, mobile network, wired or wireless network, private network or virtual private network. Figure 1Only one remote computing device 104 is shown in order to simplify and clarify the description, but it is understood that any number of client computers are supported and can communicate within the system 100.

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

[0044] In various embodiments, a hardware module can be implemented mechanically or electronically. For example, a hardware module may include dedicated circuitry or logic that is permanently configured (e.g., as 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 circuitry (e.g., as contained within a processor or other programmable processor) that is temporarily configured by software to perform certain operations. It will be appreciated that the decision to implement a hardware module mechanically, in a dedicated and permanently configured circuitry, or in a temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0045] Thus, the term "hardware module" should be understood to encompass a tangible entity, an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) so as to operate in a certain manner or perform certain operations described herein. As used herein, a "hardware-implemented module" refers to a hardware module. Contemplating embodiments in which hardware modules are temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each of the hardware modules at any one time. For example, where a hardware module includes a processor configured by software, the processor can be configured as corresponding different hardware modules at different times. The software can thus configure the processor, for example, to constitute a particular hardware module at one time and to constitute a different hardware module at a different time.

[0046] A hardware module can provide information to other hardware modules and receive information from other hardware modules. Therefore, the described hardware modules can be considered to be coupled in a communication manner. When multiple such hardware modules exist simultaneously, communication can be achieved by transmitting signals (e.g., via suitable circuits and buses) connected to the hardware modules. In an embodiment where multiple hardware modules are configured or initialized at different times, communication between these hardware modules can be achieved 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 store the output of the operation in a memory device, and the hardware module is coupled to the memory device in a communication manner. Then, another hardware module can subsequently access the memory device to retrieve and process the stored output. The hardware module can also initiate communication with an input or output device and can operate on a resource (e.g., a collection of information).

[0047] 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. Regardless of whether the configuration is temporary or permanent, the processors may constitute processor-implemented modules that operate to perform one or more operations or functions. In some example embodiments, the modules mentioned herein may include processor-implemented modules.

[0048] Similarly, the methods or routines described herein may be processor-implemented, at least in part. For example, at least some of the operations of the methods may be performed by one or more processors or processor-implemented hardware modules. The performance of certain operations may be distributed among one or more processors, not only residing in a single machine, but also deployed across multiple 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 a server farm), while in other embodiments, the processors may be distributed across multiple locations.

[0049] The one or more processors may also be operable to support the performance 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 via one or more appropriate interfaces (e.g., application program interfaces (APIs)).

[0050] The performance of certain operations can be distributed among one or more processors, not only residing within a single machine, but also deployed across multiple machines. In some example embodiments, one or more processors or processor-implemented modules can be located in a single geographic location (e.g., in a home environment, an office environment, or a server farm). In other example embodiments, one or more processors or processor-implemented modules can be distributed across multiple geographic locations.

[0051] Some parts of this specification are presented in terms of algorithms or symbolic representations of operations on data stored as bits or binary digital signals in machine memory (e.g., computer memory). These algorithms or symbolic representations are examples of techniques used by those skilled in the art of data processing to convey the substance of their work to other persons skilled in the art. As used herein, an "algorithm" is a self-consistent sequence of operations or similar processes that produce a desired result. In this context, algorithms and operations involve the physical manipulation of physical quantities. Typically, but not necessarily, such quantities can be in the form of electrical, magnetic, or optical signals that can be stored, accessed, transmitted, combined, compared, or otherwise controlled by a machine. Mainly for commonly used reasons, it is sometimes convenient to refer to such signals using words such as "data," "content," "bit," "value," "element," "symbol," "character," "item," "number," "digit," etc. However, these words are merely convenient labels and will be associated with appropriate physical quantities.

[0052] Unless specifically stated otherwise, discussions herein using words such as "process," "calculate," "compute," "determine," "present," "display," etc. may refer to the actions or processes of a machine (e.g., a computer) that controls 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, send, or display information.

[0053] As used herein, any reference to "an embodiment," "some embodiments," "an embodiment," or "teachings" means that a particular element, feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. The appearances of the phrases "in some embodiments" or "teachings" in different places in the specification are not necessarily all referring to the same embodiment.

[0054] The expressions "coupled" and "connected," as well as their derivatives, may be used to describe some embodiments. For example, the term "coupled" may be used to describe some embodiments 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.

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

[0056] By adding the ability to display user-created graphics on payment devices 600 600a, the technical problem of recalling which payment account offers which offers is solved. In the past, payment devices 600 600a could display the card issuer or other logo, but the message came from the card issuer. Using the present system and method, a graphic 680 can be created by the user and displayed on a display 660 660a on the payment device 600 600a at the time of purchase, allowing the message 680 680a to be conveyed to the user at the time of purchase. Payment devices 600 600a are physically modified to add a display 660 660a capable of displaying the graphic 680 680a.

[0057] After reading this disclosure, those skilled in the art will understand additional alternative structural and functional designs of the systems and methods described herein using the principles disclosed herein. Therefore, although specific embodiments and applications have been shown and described, it should be understood that the disclosed embodiments are not limited to the precise configurations and components disclosed herein. It will be apparent to those skilled in the art that 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.

Claims

1. A processor-implemented method for displaying a graphical object on a payment device, comprising: receiving, by a processor of a mobile computing device, a communication comprising a secure element and a graphical object corresponding to a payment device, wherein the graphical object is created by a holder of the payment device; determining, using logic in the processor, whether the graphical object conforms to an acceptable protocol; as well as In response to determining that the graphical object conforms to the acceptable protocol, transmitting, by the processor of the mobile computing device, the graphical object to the payment device for display in a display area of the payment device, Wherein displaying the graphical object includes: displaying the graphical object within a display on the payment device in response to receiving a selection of the payment device and the payment device being within a threshold distance of the mobile computing device executing a digital wallet application. 2 . The processor-implemented method of claim 1 , wherein the graphical object comprises text. 3 . The processor-implemented method of claim 1 , wherein the graphics object is formatted according to a protocol. The processor-implemented method of claim 1 , wherein the graphics object is received in response to a communication with an API. The processor-implemented method of claim 1 , wherein an application on a mobile computing device creates the graphical object. The processor-implemented method of claim 5 , wherein the application communicates with other applications on the mobile computing device.

7. The processor-implemented method of claim 6, wherein the graphical object includes data from other applications on the mobile computing device.

8. The processor-implemented method of claim 7, wherein the application extracts data from other applications to create the graphics object.

9. The processor-implemented method of claim 2, wherein receiving the graphical object comprises receiving the graphical object from an input of the digital wallet application at the mobile computing device.

10. The processor-implemented method of claim 1, wherein displaying the graphical object comprises displaying the graphical object in response to receiving a selection of a payment account for the payment device at a digital wallet application executing at the mobile computing device.

11. The processor-implemented method of claim 1 , wherein the display is integral to a portable payment device.

12. The processor-implemented method of claim 11, wherein the graphical object is transmitted to the portable payment device using wireless communication.

13. A portable computer payment system comprising a processor, a memory, a display, and input / output circuitry, wherein the processor is physically configured to: receiving, by the processor of the portable computer payment system, a communication comprising a secure element and a graphical object corresponding to a payment device, wherein the graphical object is created by a holder of the payment device; determining, using logic on the processor, whether the graphics object conforms to an acceptable protocol; as well as In response to determining that the graphical object conforms to the acceptable protocol, transmitting, by the processor of the portable computer payment system, the graphical object to the payment device for display in a display area of the payment device, Wherein displaying the graphical object includes displaying the graphical object within a display on the payment device in response to receiving a selection of the payment device and the payment device being within a threshold distance of the portable computer payment system executing a digital wallet application.

14. The computer payment system of claim 13, wherein the graphical object comprises at least one of: text, graphics, or video.

15. The computer payment system of claim 13, wherein the graphic object is formatted according to a protocol.

16. The computer payment system of claim 13, wherein an application on the portable computer payment system creates the graphical object.

17. The computer payment system of claim 16, wherein the application communicates with other applications on the portable computer payment system.

18. The computer payment system of claim 16, wherein the application extracts data from other applications to create the graphical object.

Images