Not Applicable.
Not Applicable.
The present invention generally relates to retail devices, and more particularly, to a stored value card kiosk system and method. Additionally, the present invention relates to a housing structure for housing and supporting a computing device to generate a graphical user interface (GUI) for activation of stored value cards.
Transaction cards, or stored value cards, such as pre-paid phone services, general purpose, reloadable credit/debit cards, including open loop and closed loop prepaid cards, and the like, have become popular gifts. Stored value cards typically comprise a certain cash equivalent value that is encoded upon a magnetic strip applied to the surface of the card. This stored value may be determined by the vendor prior to packaging and display for sale or is selected at the point of sale by the purchaser and loaded by the cashier using a magnetic card reader/writer. Holders for stored value cards have been used both to simply store stored value cards and to provide a surface for decorative indicia and graphics, as well as personalized or preprinted text.
Stored value cards are typically displayed in a retail outlet in their non-activated (i.e., blank) form, and only activated manually at a point-of-sale (POS) terminal of the retail outlet. Nevertheless, this manual process may be relatively costly and time consuming to the retail outlet in that manual intervention is required. Additionally, sales of these stored value cards may be encumbered due to a substantial separation between a purchase decision by the consumer and the actual purchase of these stored value cards. What is needed is a system that provides for automated activation of stored value cards at or close to a point of purchase decision point where the stored value cards are displayed.
Embodiments of the stored value card kiosk system may provide a solution to conventional stored value card purchasing systems using a graphical user interface (GUI) for activating stored value cards where these stored value cards are displayed, such as on a kiosk disposed in a retail outlet or other suitable location. The GUI is controlled by a computing device that conducts a transaction with a merchant associated with the stored value card and a financial account holder associated with the purchaser to activate the stored value card in an automated manner.
According to one aspect, a stored value card activation system includes a server in communication with one or more computing devices configured in kiosks. The server receives stored value card type information associated with one of multiple non-activated stored value cards from the computing device. The server also receives monetary amount information to be associated with the selected stored value card from the kiosk, and payment information from a user of the kiosk. From this information, the server conducts a financial transaction with a financial account server associated with an account of the user, and activates the selected stored value card in accordance with the financial transaction.
According to another aspect, a kiosk includes a housing structure and a computing device in communication with a server. The computing device receives stored value card type information associated with one of multiple non-activated stored value cards. The computing device also receives monetary amount information to be associated with the selected stored value card, and payment information from the user for conducting a financial transaction with a financial account server associated with an account of the user, and activating the selected stored value card in accordance with the financial transaction.
According to another aspect, a stored value card activation method includes receiving stored value card type information associated with a selected one of the plurality of non-activated stored value cards from a computing device configured in a kiosk, monetary amount information to be associated with the selected stored value card from the kiosk, and payment information from a user of the kiosk. From this information, the method conducts a financial transaction with a financial account server associated with an account of the user, and activates the selected stored value card in accordance with the financial transaction.
Although stored value cards have been become a commonly accepted gifting medium, their use has not been without limitation. For example, conventionally implemented stored value cards typically require manual intervention for their activation. Embodiments of the present disclosure provide a solution to this problem with a stored value card kiosk that provides for activation of stored value cards via a housing structure that supports a display that generates a graphical user interface (GUI) from which stored value cards may be activated. Embodiments may include an online, interactive activation platform, whereby a computing device configured in a kiosk may send and receive digital messages for activating the stored value card by a merchant associated with the stored value card and conducting a transaction with a financial account (e.g., credit card account) associated with the user.
The computing device 103 generates a graphical user interface (GUI) to the display 104 for providing interaction with a user (e.g., a stored value card consumer). The floorstand housing 102 has a bottom end 106 for support from and/or mounting to a floor, and is dimensioned such that a user having a standard height may access the GUI in a relatively comfortable manner. In the particular embodiment shown, for example, the floorstand housing 102 has a height of 59 and ⅞ inches, a width of 15 inches, and a depth of 12 and ⅝ inches. Nevertheless, other embodiments of the floorstand housing 102 may have other dimensions without departing from the spirit or scope of the present disclosure. For example, other embodiments of the floorstand housing 102 may have a height greater or less than 59 and ⅞ inches, a width greater or less than 15 inches, and/or a depth of greater or less than 12 and ⅝ inches.
The floorstand housing 102 may be made of any suitable material, such as wood, plastic, composites, and/or metal, that supports the computing device 103 and display 104 in a structurally sound manner. The floorstand housing 102 may also include one or more pockets 108 for housing various ancillary items, such as non-activated stored value cards and/or paraphernalia associated with stored value cards. The stored value cards may be any type of card that may be associated with a monetary amount to be redeemed for one or more products or services. Examples of such stored value cards include for example, pre-paid phone service cards, general purpose credit cards, debit cards, and the like.
Each pocket 108 includes a cavity into which the ancillary items may be placed, and is formed of a generally rigid material, such as sheet metal that is attached to the side of the housing 102. Nevertheless, other embodiments may include any type of housing structure for housing ancillary items associated with the activation of stored value cards. The kiosk 100 also includes an optional camera 110 for surveillance purposes and a card reader 112 as will be described in detail below. Additionally, the kiosk 100 may include a cash processing unit 114 that receives cash payment from the user, and dispenses monetary change for any cash amount received in excess of the required transaction fee for activating the stored value card. The particular embodiment shown merely describes one arrangement of the display 104, pockets 108, camera 110, card reader 112, and cash processing unit 114 configured on the housing 102 and that other arrangements may be provided without departing from the spirit and scope of the present invention. For example, the camera 110 may be configured at any desired position and orientation on the housing 102 for gathering images of ambient surroundings of the housing 102, such as consumers who may use the stored value card activation system 100.
The server 202 communicates with a web site of a retailer, such as a mail order retailer, or processing center of a retailer or other entity that processes incoming orders for products and fulfills these orders by managing shipment of the ordered product to the purchaser or other recipient and payment for the ordered product from the purchaser. The server 202 includes a processing system 302 (
In one embodiment, the server 202 communicates with a financial account server 210 that is associated with a financial account of the user to provide payment for the activated stored value card by the user. The server 202 may also communicate with the computing device 103 to receive cash payment via the cash processing unit 114. The financial account may be any type, such as a credit card account, a debit card account, or a PAYPAL™ account. Prior to activation of the stored value card, the server 202 facilitates a financial transaction between the stored value card validation server 208 and the financial account server 210 associated with the user to provide payment for the stored value card. The stored value card validation server 208 and the financial account server 210 have one or more processors and executable instructions stored in volatile and/or non-volatile memory for performing the actions and/or steps described herein.
In another embodiment, the server 202 provides stored value card type information, monetary amount information, and payment information to the stored value card activation server 208 such that the stored value card activation server 208 conducts the transaction by communicating with the financial account server 210 and activating the stored value card associated with the transaction. For example, the server 202, upon receipt of stored value card type information, monetary amount information, and payment information from the computing device 104, transmits this information to a website of the merchant hosted on the stored value card validation server 208. In turn, the website executes an process that negotiates the transaction with the financial account server 210 of the consumer, activates the selected stored value card, and transmits one or more messages back to the computing device 104 indicating whether or not the transaction has succeeded or not.
The computing device 103 has one or more processors and volatile and/or non-volatile memory. Examples of a computing device 103 include one or more personal computers, mobile computers and/or other mobile devices, and other computing devices. In one embodiment, the computing device comprises a tablet computer. The computing device 103 may communicate via wireless and/or wireline communications.
The data source 206 stores activation history files 230 including activation information associated with each transaction that may be tracked and stored. Although the data source 206 is shown as being located on, at, or within the local server 202, it is contemplated that the data source 206 can be located remotely from the local server 202 in other aspects of the system 200, such as on, at, or within a database of a data management system or a database of another computing device or system having at least one processor and volatile and/or non-volatile memory. In one embodiment, the data source 206 comprises a relational database management system, such as a MySQL-based database structure that provides a front end for entry and access of data stored therein and provides for replication for increased reliability and/or mirroring by other sites that use the stored value card kiosk 100.
The communication network 220 can be the Internet, an intranet, or another wired and/or wireless communication network. In one aspect, one or more of the server 202 and the computing device 103 communicate with one another using any suitable protocol or messaging scheme. For example, the server 202 and computing device 103 may communicate using a Hypertext Transfer Protocol (HTTP), extensible markup language (XML), extensible hypertext markup language (XHTML), or a Wireless Application Protocol (WAP) protocol. Other examples of communication protocols exist. Although the example of
The computing device 103 may also include a graphical user interface (or GUI) application 246, such as a browser application, or application software (i.e., a mobile app) stored in the memory 242 and executed on the processors 240 to generate a graphical user interface 248 to the display 104. The graphical user interface 242 enables the computing device 103 of the user to interact with one or more data entry forms received from the server 202 to enter order detail data and submit orders to the application 204 for the purpose of activating a stored value card that may be sent to the recipient 216.
In one embodiment, the computing device 103 is a commercial off-the-shelf (COTS) computing device, such as a personal computer, a mobile computer, a tablet computer, a mobile device, and/or other computing device that is configured in or on the housing 102 using one or more mounting mechanisms, such as screws, bolts, hooks, zip ties, adhesives, track system, or other mechanism, such as one that maintains the computing device in or on the housing 102 using a tensioning mechanism. Such as COTS device includes a charging tether for providing power to the computing device, and/or a security or lasso tether to prevent its theft.
In another embodiment, the computing device 103 includes a custom design with the display 104, audio generation device 246, processors 240, and memory 242 individually integrated into the housing 102. For example, the display 104 and audio generation device 246 may be mounted on a surface of the housing 102 using a suitable attachment mechanism for providing advertising content to consumers. Example of such attachment mechanisms include, for example hinges and/or adhesives, such as weldment, hot glue, epoxy, and the like. Another example includes a housing 102 made of plastic that includes tabs integrally formed on the housing that hold the display 104 and audio generation device 246 in or on the housing 102 using a press-type fit. Yet another example includes tabs integrally formed on the housing 102 that are bent by the application of heat to secure the display 104, audio generation device 246, processors 240, and/or memory 242 to the housing 102.
In a particular embodiment, the computing device 103 is a tablet computer and the advertising content display application 248 is embodied as application software (i.e., an app) designed to be executed on the computing device 103. The operating software may be configured as a permissions-based format such that only the app is allowed to execute for administering the stored value card advertising system 100. That is, consumers may be inhibited from executing any other application on the computing device 103. Additionally, the app may be locked (i.e., inhibited from executing) in response to detection of a tampering event and/or due to malfunction of the system. The stored value card advertising server 102 may also include administrator privileges (e.g. super user mode) that can be accessed via a unique key combination (e.g., password access) for servicing, maintaining, or otherwise administering the operation of the computing device 103. The tablet computer may be configured on the housing 102 such that its display is oriented in either a landscape mode or a portrait mode.
According to one aspect, the stored value card activation server 202 includes a computer readable media 304 on which the stored value card activation application 204 and data source 106 are stored. The stored value card activation application 204 includes instructions or modules that are executable by the processing system 302 to generate customized stored value cards to be sent to recipients.
The computer readable media 304 may include volatile media, nonvolatile media, removable media, non-removable media, and/or another available media that can be accessed by the stored value card activation server 202. By way of example and not limitation, computer readable media 304 comprises computer storage media and communication media. Computer storage media includes non-transient storage memory/media, volatile media, nonvolatile media, removable media, and/or non-removable media implemented in a method or technology for storage of information, such as computer/machine readable/executable instructions, data structures, program modules, and/or other data. Communication media may embody computer readable instructions, data structures, program modules, or other data and include an information delivery media or system.
A GUI interface module 306 facilitates the receipt of data and/or other communications from the computing device 103 of the kiosk 102. In one example, the computing device 103 executes a graphical user interface (GUI) that displays an interactive display, or other suitable user interface mechanism including one or more selectable fields, editing screens, and the like for receiving instructions and data and activating the card by the user (i.e., sender).
A user financial account API module 308 communicates with a payment processing server, such as the financial account server 210, to transact a monetary transfer of funds from the user's financial account to a financial account of a merchant of the stored value card.
The stored value card validation API module 310 communicates with the stored value card activation server 208 for activation of the stored value card. For example, the stored value card activation server 208 may be a server managed by a merchant associated with the stored value card. For another example, the stored value card activation server 208 may be a third party server of a third party stored value card activation service for activation of the stored value card. Examples of such third party stored value card activation service include INCOMM™, SVS™, FIRST DATA™, and STORE FINANCIAL™ stored value card activation services.
In one embodiment, the stored value card validation API module 310 communicates with a specified stored value card activation server from among multiple stored value card activation servers 208 according to the stored value card type information received from the computing device 103. For example, merchants often delegate the activation of their stored value cards to one or more of the available third party activation services such as those described above. Thus, a particular third party activation service may, or may not, be configured to process stored value card transactions of stored value cards associated with a particular merchant. Moreover, certain merchants may have a preferred certain stored value card activation service to be designated as a primary source, and one or more other stored value card activation services to be designated as secondary sources to be used only when the primary source is not available. The stored value card validation API module 310, upon receipt of stored value card type information from the computing device 103, communicates with a particular stored value card activation server specified for use with that merchant using the stored value card type information. For example, the stored value card validation API module 310 may include a lookup table that associates the merchant of each stored value card with a particular stored value card activation service. Additionally, the lookup table may associate each merchant with a preferred field indicating a primary stored value card activation source and a secondary field indicating secondary stored value card activation sources to use in the primary source is not available.
A remote management module 312 communicates with the computing device 103 of the kiosk 100 to manage various aspects of its operation. For example, the remote management module 314 may communicate with the computing device 103 to ensure its proper operation, and disable the computing device 103 from further operation if a failure or malfunction is detected. In one embodiment, the remote management module 312 may erase the memory of the computing device 103 if a fraudulent event is detected. Also, the remote management module 312 may provide for remote access to the computing device 103 from the stored value card activation server 202. The remote management module 314 may also communicate with the computing device 103 to administer software updates to the computing device 103.
In one embodiment, the remote management module 312 may communicate with one or more sensors of the kiosk 100 for surveillance and/or fraud detection purposes. For example, the remote management module 312 may receive images and/or video information from a camera of the kiosk 100. During a stored value card activation procedure described herein, the camera may take an image of the user at periodic intervals (e.g., 5 second intervals) and/or at events, such during user input or selection of certain fields, and the computing device 103 stores the images for future reference in the event that a fraudulent event is detected at a later time. Alternatively, the computing device 103 transmits the images to a stored value card activation server 202 for storage in the data source 206.
In another embodiment, the remote management module 312 generates a GUI 320 that displays various activities and provides for administrative control of one or more computing devices 103 of the kiosk 100 from the stored value card activation server 202. For example, the GUI 320 may be generated in the form of a dashboard in which multiple characteristics of each of multiple computing devices 103 may be monitored and controlled. The GUI 320 is generated on the display 303 of the server 202 and various fields of the GUI 320 controlled via the input device 322 of the server 202.
The GUI 320 may display various characteristics of each computing device 103, such as an index to any log files associated with the operation of its respective computing device 103. For example, the log files may include sales data, location data obtained via a location detection device (e.g., global positioning system (GPS) device) of the computing device 103, device health, a history of fraudulent alerts, and any images/video obtained via the camera of the kiosk 100.
Additionally, the GUI 320 may receive user input via the input device 322 to control the operation of the computing device 103. For example, an administrator may, from the display 303 and input device 322 of the server 202, control the computing device 103 to inhibit or allow certain functionality, perform periodic maintenance on the computing device 103, and/or access one or more log files associated with the operation of the computing device 103.
An auditing and tracking module 314 maintains a historical record of transactions conducted through the use of the kiosk 100 by storing the transactions in the activation history files 230. For example, the auditing and tracking module 314 may periodically report (or report upon demand) usage information associated with the kiosk 100. This usage information may include, for example, which type of stored value cards are most often activated and a distribution of how much money is activated on these cards. Information such as this may be useful for distribution to merchants that offer stored value cards to solicit their further use of the stored value card kiosk 100.
A stored value card activation module 316 facilitates the activation of the stored value card by managing the activation of the stored value card by the stored value card activation server 208, and handling the financial transaction from the financial account server 210 of the user to the account of the merchant that issued the stored value card. The stored value card activation module 316 may either receive payment from the user via a financial account server 210 associated with the user, or may receive cash payment for the stored value card via the cash processing unit 114. For example, if the stored value card activation module 316 receives information from the computing device 103 indicating that the user wishes to dispense cash for activation of the stored value card, the stored value card activation module 316 communicates with the cash processing module 114 to accept a monetary amount for the stored value card from the user. Alternatively, if the stored value card activation module 316 receives information from the computing device 316 indicating that the user wishes to conduct an electronic monetary transaction, the stored value card activation module 316 may then communicate with user financial account API module 308 to conduct an electronic financial transaction with a financial account server of the user.
A physical stored value card or a digital stored value card (e-stored value card) may be activated. In one embodiment, an e-stored value card may be generated in digital form and transmitted to the recipient via any suitable communication mechanism, such as via an e-mail message or a short message service (SMS) message. The e-stored value card may be printable in a form suitable for redemption at a retail outlet of a merchant associated with the e-stored value card. In another embodiment, a non-activated physical stored value card may be activated by swiping the physical stored value card 212 using the card reader 112 of the kiosk 100.
It should be appreciated that the modules described herein are provided only as an example of a computing device that may execute the stored value card activation application 204 according to the teachings of the present invention, and that other computing devices may have the same modules, different modules, additional modules, or fewer modules than those described herein. For example, one or more modules as described in
In step 402, a GUI is generated to the display of the computing device 103 of the kiosk 100. The computing device 103 may function as a thin client such that the stored value card activation application 204 administers the generation of the GUI on the computing device 103. In another embodiment, the computing device 103 includes instructions in its memory for generating the GUI on its display, such as by application software (i.e., an app) designed to be executed on the computing device 103 embodied as a tablet computer or other similar type of portable computing device. In another example, the GUI module is on the stored value card activation server 202, and the stored value card activation server generates the GUI screens to the display of the computing device 103.
According to one aspect, the application 204 generates an advertising screen (
As another example, marketing content (e.g., advertisements, special offers, etc.) may be displayed on any of the screens described herein for view by the user. The marketing content may be displayed while performing the process, or while the computing device 103 is idly waiting to be used by the next user. The marketing content may be pushed to the computing device 103 from the stored value card activation server 102 on an on-demand type basis. For example, the administrator of the stored value card activation server 102 may selectively push marketing content to be displayed based upon monetary payment of the merchant to be advertised. Thus, the marketing content may be pushed onto one, all, or only a selected subset of computing devices 104. The marketing content may be presented in any suitable form, such as a video segment, an animation, a text message, audio message, or any combination thereof. Additional details related to generating advertising content to be displayed on the computing device are described in U.S. patent application Ser. No. 13/946,749, filed Jul. 19, 2013, and entitled “Stored Value Card Display Advertising System and Method,” which is hereby incorporated herein by reference in its entirety.
The advertising screen (
In step 404, the stored value card activation application 204 receives selection of a stored value card from the computing device 103. For example, the application 204 may generate a gift card type selection screen (
If a physical gift card type is selected, the gift card application 204 may generate a gift card selection screen (
The gift card type selection screen also includes other features, such as a view window 802, a video capture window 804, and a “Go Back” button 806 that causes the application 204 to revert back to the previously displayed screen. The view window 804 displays useful or entertaining information to the consumer, such as an instructional video demonstrating how a stored value card which has been selected by the consumer is to be swiped through the card reader 112. Nevertheless, the view window 802 may display any desired content for view by the consumer, such as an advertisement for enhancing appeal of the stored value cards. The video capture window 804 displays video imagery obtained by the camera 110. Certain embodiments of the video capture window 804 may deter theft or vandalism by showing to consumers that their actions are being monitored by the system.
If a digital gift card rather than a physical gift card is selected by the consumer, the application 204 generates a recipient information entry screen (
In one embodiment, the stored value card activation application 204 may receive personalized stored value card information, such as customized textual, audio, images, photographic, and/or video content to be included with the stored value card. For example, the stored value card activation application 204 may receive customized content, such as an audio or video segment recorded by a microphone or camera, respectively configured on the computing device 103 to be included with an e-stored value card to be delivered to the recipient. As another example, the stored value card activation application 204 may receive location information from the computing device 103 and generate customized content to be included with the stored value card, such as a background image commemorating a particular location at which the kiosk 100 is placed. Additional details related to personalizing the stored value card according to user-supplied content received from the user are described in U.S. Provisional Patent Application Ser. No. 61/737,731, filed Dec. 14, 2012, and entitled “Online Personalized Gifting System,” which is a continuation in part of application Ser. No. 13/273,220, filed Oct. 13, 2011, and entitled “Online Personalized Gifting System.” The contents of 61/737,731 and Ser. No. 13/273,220 are both incorporated herein by reference in their entirety.
In step 406, the stored value card activation system receives a monetary amount to be assigned to the gift card. When gift card type information has been entered, a gift card amount selection screen (
In one embodiment, the application 204 stores information in the data source 206 for each merchant indicating the various predetermined amounts that may be provided for gift cards from that merchant and whether or not the merchant allows customized monetary values to be allocated to their gift cards. When the gift card amount selection screen is displayed, the application 204 displays those values in the amount selection window 1002 and the entry field 1006 for entry of a customized monetary amount if the merchant support such an amount.
Following receipt of a monetary amount to be associated with the gift card, the application displays a confirmation screen (
In step 408, the stored value card activation application 204 receives payment from the user. For example, the stored value card activation application 204 may generate a payment selection screen (
The stored value card activation application 204 may also generate a confirmation screen (
In step 410, the stored value card activation application 204 facilitates activation of the gift card. In one embodiment, the server 202 communicates with a financial account server 210 of the user to provide payment for the activated gift card by the user. In another embodiment, the server 202 provides gift card type information, monetary amount information, and payment information to the stored value card activation server 208 such that the stored value card activation server 208 conducts the transaction by communicating with the financial account server 210 and activating the gift card associated with the transaction. For example, the stored value card activation application 204 may display a purchase confirmation screen (
In one embodiment, the purchase confirmation screen includes a SMS entry field 1702, an email entry field 1704, and a “No Thanks” button 1706 to be selected by the user when a receipt for the transaction is not desired by the user. The entry field 1702 and the email address entry field 1704 for entry of either a phone number or an email address of the user for sending a receipt associated with the completed transaction. When either the SMS entry field 1702, the email entry field 1704, or the “No Thanks” button 1706 is entered by the user, the application 204 then displays a thank you screen (
The application 204 may repeat the above-described steps to activate other stored value cards for the same user or other users. Nevertheless, when use of the stored value card activation system is no longer needed or desired, the process ends.
It should be appreciated that the steps described herein are provided only as an example of a process that is performed by the stored value card activation application 204 according to the teachings of the present invention, and that the stored value card activation application 204 may perform fewer, more, or different types of steps than those described herein. For example, the stored value card ordering application 204 performs multiple steps described above as a single step, or perform a single step as multiple, distributed steps. As another example, certain steps described herein is performed by other components of the stored value card activation system 200, such as by the computing device 108 used by the user, the stored value card activation server 208, and/or the financial account server 210 of the user.
In one embodiment, the stored value card activation application 204 may also possess the capability of locking (e.g., disabling) the computing device 103 in the event that a fault condition occurs or a fraudulent event is detected. For example, if a particular user attempts to process the transaction using an invalid credit card for a specified number of times, the stored value card activation application 204 may disable the computing device 103, display a lockdown screen (
In another embodiment, the stored value card activation system 100 may include one or more security features. The stored value card activation server 202 may receive and store images that are received periodically (e.g., every five seconds) or received at certain events using the camera 110 mounted on the kiosk 100. The images may be stored for a specified amount of time such that personnel who administer the use of the stored value card activation system 100 may forensically may obtain facial identification of the fraudulent user.
For a particular embodiment in which the computing device 103 is a tablet computer, a specified executable application (i.e., an app) may be used to generate the GUI from which information is received from the user. The operating software may be configured as a permissions-based format such that the user is only allowed to execute the app for administering the stored value card activation system 100. That is, the user is inhibited from executing any other application on the computing device 103. Additionally, the app may be locked (i.e., inhibited from executing) in response to detection of a fraudulent event and/or due to malfunction of the system. The stored value card activation server 102 may also include a GUI such that an administrator of the stored value card activation system 100 may remotely access the computing device 103, and have administrative privileges (e.g. super user mode) that can be accessed via a unique key combination (e.g., password access) for servicing, maintaining, or otherwise administering the operation of the computing device 103. The tablet computer may also be physically coupled to a tether or cable to prevent its theft.
The counter-top housing 2002 has a bottom end 2006 for support from and/or mounting to a typical counter-top, and is dimensioned such that a user may access the GUI in a relatively comfortable manner. In the particular embodiment shown, for example, the counter-top housing 2004 has a height of 10.406 inches, a width of 12.688 inches, and a depth of 5.375 inches. Nevertheless, other embodiments of the counter-top housing 2004 may have other dimensions without departing from the spirit or scope of the present disclosure. For example, a wall-mounted housing, floorstand, or free standing housing may be used.
The counter-top housing 2004 may be made of any suitable material, such as wood, composites, plastic, and/or metal that supports the computing device 2002 in a structurally sound manner. The counter-top housing 102 may also include one or more pockets 2008, shelves, or containers for housing various ancillary items, such as blank (non-activated) stored value cards and/or paraphernalia associated with stored value cards.
The particular retail display housing 2104 as shown has a floorstand-like structure with a bottom end 2106 for support from a floor. In other embodiments, retail display housing 2104 may be dimensioned for support from any suitable surface, such as, for example, a counter-top, a floor, a shelf, or a wall. The retail display housing 2104 may be made of any suitable material, such as wood, plastic, composites, and/or metal, that supports the computing device 2102 in a structurally sound manner. The retail display housing 2104 may also include multiple regularly spaced holes that are designed to accept hooks 2108 for hanging other retail sale items, such as stationary, postcards, or other gifting paraphernalia.
The retail display housing 2104 includes a chassis 2110 for securing the computing device 2102 to the retail display housing 2104. The chassis 2110 generally includes a front plate 2112 and a back plate 2114 that securely confine the computing device 2102 therebetween using tamper resistant screws 2116. The front plate 2112 and back plate 2114 include hooks 2118 that, when inserted into holes of the retail display housing 2104, prevent removal of the chassis 2110 from the retail display housing 2104.
The chassis 2204 as shown has a third party display mounting structure with hooks 2206 to be supported from holes in a third party display. The third party display may be any retail display structure that is configured to display retail items. Examples of such third party displays may include, for example, the retail display housing 2104 of
The computing device 2204 may be any type and size. In one example, the computing device 2204 is a tablet computer having a 7.0 inch display size. A tablet computer having such a size may be well accommodated into certain stored value card display corner posts.
The chassis 2204 may be made of any suitable material, such as wood, plastic, composites, and/or metal, that supports the computing device 2202 on a wall in a structurally sound manner. The retail display housing 2202 also includes two pegs 2208 for supporting and displaying stored value cards 2210 in close proximity to the computing device 2202. Nevertheless, any quantity of pegs 2208 may be used.
The chassis 2204 with a front plate 2212 and a back plate 2214 for secure confinement of the retailer computing device 2202 using one or more tamper resistant screws 2216 such that the computing device 2203 is securely mounted to an outer surface of a wall on which the retail display housing 2200 is hung. The front plate 2212 includes a display hole to provide visibility of the display from in front of the retail display structure. Additionally, the tamper resistant screws 2216 may be configured on the chassis 2204 such that they may also extend through a wall on which the chassis 2204 is hung to secure the chassis 2204 to the wall.
The chassis 2204 has a depth D that supports the computing device 2202 at a specified distance in front of the wall on which it is mounted. In the particular embodiment shown, the chassis 2204 has a depth of approximately 2.0 inches for supporting the computing device 2202 in front of a wall on which it is mounted. Nevertheless, other embodiments of the chassis 2204 may have any desired depth D without departing from the spirit or scope of the present disclosure. Embodiments that support the computing device 2204 a specified depth in front of a wall may provide an advantage in that the computing device 2202 may be maintained closer to customers for increased eye appeal. Additionally, the chassis 2204 requires relatively little floor space at a retail location; that is, it may be configured on an existing display shelf or other structure in a retail location without the use of any additional support structure that consumes floor space.
In one embodiment, the chassis 2204 provides a closed frame around the computing device 2204 such that the top and the back of the computing device 2204 is covered, thus restricting access to these portions of the computing device 2204. Additionally, the chassis 2204 is formed such that, when the computing device 2204 is housed therein, only certain physical ports of the computing device 2204 are accessible. That is, the front plate 2212 and/or back plate 2214 may include one or more tabs for concealing physical ports that are to be restricted from access when the computing device 2204 is housed in the chassis 2204. For example, the chassis 2204 may include a tab or other physical feature that covers certain critical buttons of the computing device 2202, such as its “home” button or power button, to prevent their actuation.
As best shown in
Preferably, the graphic image 2308 includes advertising content that promotes the sales of gift cards 2312 displayed on the kiosk 2300. For example, the graphic image 2308 includes an animated image and overlaying text portraying some positive trait of at least one of the gift cards 2312 displayed on the kiosk 2300. The graphic image 2308 as shown is formed on a generally rectangular-shaped piece of card stock that is mounted to the display region 2306 using releasable adhesive or other releasable attachment means.
The particular stored value card kiosk 2404 as shown has a wall-mount structure adapted for hanging from a wall using any suitable mounting mechanism. For example, the kiosk 2404 includes holes in the housing 2404 that are configured to accept anchors or screws that may be secured to a wall. Another example mounting mechanism includes one or more pegs that are shaped for insertion into a track mounting system or other system having a slot or depression that entraps the pegs. Other example of suitable mounting mechanisms may include adhesives, suction cups, magnets, zip ties, and the like.
The stored value card kiosk 2404 includes one or more pockets 2406 for holding stored value cards 2408 is close proximity to the computing device 2402. The pockets 2406 are formed of a 0.060 inch thick sheet of transparent material, such as glycol-modified polyethylene terephthalate (PETG), although any suitable material may be used. Each pocket is approximately 2.0 inches deep for securely holding the stored value cards while allowing partial exposure so that they may be easily removed by users.
Several embodiments including the floorstand housing, the counter-top housing, the retail display unit, the wall mount housing, and the third party attachment housing have been described above for providing a structure for facilitating a stored value card advertising platform. Nevertheless, it should be understood that the afore-described housings may have additional, fewer, or different features than described herein. For example, other embodiments of the counter-top housing, the retail display unit, the wall mount housing, or the third party attachment housing may have different dimensions than the embodiments described above. As another example, other embodiments of the counter-top housing, the retail display unit, the wall mount housing, or the third party attachment housing may have more than one computing device (e.g., two or more computing devices) configured thereon for displaying advertising content for consumers. As yet another example, other embodiments of the counter-top housing, the retail display unit, the wall mount housing, or the third party attachment housing may include one, both, or none of the card reader 112, and/or cash processing unit 114 that is used for processing transactions with consumers who use the stored value card kiosk.
Those skilled in the art will appreciate that variations from the specific embodiments disclosed above are contemplated by the invention. The invention should not be restricted to the above embodiments, but should be measured by the following claims.
This application is a continuation application of U.S. patent application Ser. No. 13/946,679, filed Jul. 19, 2013, now U.S. Pat. No. 10,217,107, entitled “Stored Value Card Kiosk System and Method,” which claims priority to U.S. Provisional Patent Application Ser. No. 61/818,789, filed May 2, 2013, entitled “Gift Card Kiosk System and Method,” the contents of which are incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
794417 | Maniachi | Jul 1905 | A |
3288350 | Kushner | Nov 1966 | A |
4068213 | Nakamura et al. | Jan 1978 | A |
4482802 | Aizawa et al. | Nov 1984 | A |
4734858 | Schlafly | Mar 1988 | A |
4747049 | Richardson et al. | May 1988 | A |
4755940 | Brachtl et al. | Jul 1988 | A |
4767917 | Ushikubo | Aug 1988 | A |
4795892 | Gilmore et al. | Jan 1989 | A |
4877947 | Mori | Oct 1989 | A |
4900904 | Wright et al. | Feb 1990 | A |
4908521 | Boggan et al. | Mar 1990 | A |
4943707 | Boggan | Jul 1990 | A |
5091634 | Finch et al. | Feb 1992 | A |
5117355 | McCarthy | May 1992 | A |
5202826 | McCarthy | Apr 1993 | A |
5255182 | Adams | Oct 1993 | A |
5256863 | Ferguson et al. | Oct 1993 | A |
5311424 | Mukherjee et al. | May 1994 | A |
5367148 | Storch et al. | Nov 1994 | A |
5375240 | Grundy | Dec 1994 | A |
5383113 | Kight et al. | Jan 1995 | A |
5384449 | Peirce | Jan 1995 | A |
5465288 | Falvey et al. | Nov 1995 | A |
5477038 | Levine et al. | Dec 1995 | A |
5500513 | Langhans et al. | Mar 1996 | A |
5502765 | Ishiguro et al. | Mar 1996 | A |
5511114 | Stimson et al. | Apr 1996 | A |
5577109 | Stimson et al. | Nov 1996 | A |
5581064 | Riley et al. | Dec 1996 | A |
5590038 | Pitroda | Dec 1996 | A |
5602377 | Beller et al. | Feb 1997 | A |
5619559 | Kennedy | Apr 1997 | A |
5621201 | Langhans et al. | Apr 1997 | A |
5621787 | McKoy et al. | Apr 1997 | A |
5644721 | Chung et al. | Jul 1997 | A |
5657389 | Houvener | Aug 1997 | A |
5671279 | Elgamal | Sep 1997 | A |
5679938 | Templeton et al. | Oct 1997 | A |
5679940 | Templeton et al. | Oct 1997 | A |
5696909 | Wallner | Dec 1997 | A |
5699528 | Hogan | Dec 1997 | A |
5705798 | Tarbox | Jan 1998 | A |
5708780 | Levergood et al. | Jan 1998 | A |
5721768 | Stimson et al. | Feb 1998 | A |
5721781 | Deo et al. | Feb 1998 | A |
5729693 | Holda-Fleck | Mar 1998 | A |
5732136 | Murphree et al. | Mar 1998 | A |
5734719 | Tsevdos et al. | Mar 1998 | A |
5740915 | Williams | Apr 1998 | A |
5754655 | Hughes et al. | May 1998 | A |
5760381 | Stich et al. | Jun 1998 | A |
5777305 | Smith et al. | Jul 1998 | A |
5799285 | Klingman | Aug 1998 | A |
5806045 | Biorge et al. | Sep 1998 | A |
5828740 | Khuc et al. | Oct 1998 | A |
5844972 | Jagadish et al. | Dec 1998 | A |
5850217 | Cole | Dec 1998 | A |
5857175 | Day et al. | Jan 1999 | A |
5873072 | Kight et al. | Feb 1999 | A |
5878401 | Joseph | Mar 1999 | A |
5884271 | Pitroda | Mar 1999 | A |
5889270 | Haagen et al. | Mar 1999 | A |
5889863 | Weber | Mar 1999 | A |
5897625 | Gustin et al. | Apr 1999 | A |
5903633 | Lorsch | May 1999 | A |
5903830 | Joao et al. | May 1999 | A |
5903874 | Leonard et al. | May 1999 | A |
5907142 | Kelsey | May 1999 | A |
5909492 | Payne et al. | Jun 1999 | A |
5913210 | Call | Jun 1999 | A |
5918213 | Bernard et al. | Jun 1999 | A |
5930363 | Stanford et al. | Jul 1999 | A |
5945653 | Walker et al. | Aug 1999 | A |
5950173 | Perkowski | Sep 1999 | A |
5953710 | Fleming | Sep 1999 | A |
5956695 | Carrithers et al. | Sep 1999 | A |
5956700 | Landry | Sep 1999 | A |
5968110 | Westrope et al. | Oct 1999 | A |
5984508 | Hurley | Nov 1999 | A |
5988509 | Taskett | Nov 1999 | A |
5991413 | Arditti et al. | Nov 1999 | A |
5991748 | Taskett | Nov 1999 | A |
5991749 | Morrill, Jr. | Nov 1999 | A |
5999624 | Hopkins | Dec 1999 | A |
6000608 | Dorf | Dec 1999 | A |
6012049 | Kawan | Jan 2000 | A |
6018570 | Matison | Jan 2000 | A |
6025780 | Bowers et al. | Feb 2000 | A |
6029139 | Cunningham et al. | Feb 2000 | A |
6029141 | Bezos et al. | Feb 2000 | A |
6029151 | Nikander | Feb 2000 | A |
6032135 | Molano et al. | Feb 2000 | A |
6032859 | Muehlberger et al. | Mar 2000 | A |
6039244 | Finsterwald | Mar 2000 | A |
6049778 | Walker et al. | Apr 2000 | A |
6055511 | Luebbering et al. | Apr 2000 | A |
6055567 | Ganesan et al. | Apr 2000 | A |
6058300 | Hanson | May 2000 | A |
6058382 | Kasai et al. | May 2000 | A |
6062472 | Cheung | May 2000 | A |
6070150 | Remington et al. | May 2000 | A |
6085167 | Iguchi | Jul 2000 | A |
6085242 | Chandra | Jul 2000 | A |
6088682 | Burke | Jul 2000 | A |
6092053 | Boesch et al. | Jul 2000 | A |
6098053 | Slater | Aug 2000 | A |
6105008 | Davis et al. | Aug 2000 | A |
6119164 | Basche | Sep 2000 | A |
6125352 | Franklin et al. | Sep 2000 | A |
6129276 | Jelen et al. | Oct 2000 | A |
6134533 | Shell | Oct 2000 | A |
6138106 | Walker et al. | Oct 2000 | A |
6138911 | Fredregill et al. | Oct 2000 | A |
6142369 | Jonstromer | Nov 2000 | A |
6148249 | Newman | Nov 2000 | A |
6167387 | Lee-Wai-Yin | Dec 2000 | A |
6169890 | Vatanen | Jan 2001 | B1 |
6173272 | Thomas et al. | Jan 2001 | B1 |
6175823 | Dusen | Jan 2001 | B1 |
6185545 | Resnick et al. | Feb 2001 | B1 |
6188752 | Lesley | Feb 2001 | B1 |
6219652 | Carter et al. | Apr 2001 | B1 |
6222914 | McMullin | Apr 2001 | B1 |
6226364 | O'Neil | May 2001 | B1 |
6240397 | Sachs | May 2001 | B1 |
6256690 | Carper | Jul 2001 | B1 |
6282566 | Lee, Jr. et al. | Aug 2001 | B1 |
6285749 | Manto | Sep 2001 | B1 |
6289322 | Kitchen et al. | Sep 2001 | B1 |
6295522 | Boesch | Sep 2001 | B1 |
6304860 | Martin, Jr. et al. | Oct 2001 | B1 |
6308887 | Korman et al. | Oct 2001 | B1 |
6311165 | Coutts et al. | Oct 2001 | B1 |
6311170 | Embrey | Oct 2001 | B1 |
6314171 | Dowens | Nov 2001 | B1 |
6315195 | Ramachandran | Nov 2001 | B1 |
6317028 | Valiulis | Nov 2001 | B1 |
6324525 | Kramer et al. | Nov 2001 | B1 |
6327577 | Garrison et al. | Dec 2001 | B1 |
6330544 | Walker et al. | Dec 2001 | B1 |
6332135 | Conklin et al. | Dec 2001 | B1 |
6333976 | Lesley | Dec 2001 | B2 |
6334116 | Ganesan et al. | Dec 2001 | B1 |
6360254 | Linden et al. | Mar 2002 | B1 |
6363362 | Burfield et al. | Mar 2002 | B1 |
6363364 | Nel | Mar 2002 | B1 |
6366893 | Hannula et al. | Apr 2002 | B2 |
6375073 | Aebi et al. | Apr 2002 | B1 |
6422462 | Cohen | Jul 2002 | B1 |
6424706 | Katz et al. | Jul 2002 | B1 |
6434238 | Chaum et al. | Aug 2002 | B1 |
6442532 | Kawan | Aug 2002 | B1 |
6467684 | Fite et al. | Oct 2002 | B2 |
6473500 | Risafi et al. | Oct 2002 | B1 |
6473739 | Showghi et al. | Oct 2002 | B1 |
6494367 | Zacharias | Dec 2002 | B1 |
6502745 | Stimson et al. | Jan 2003 | B1 |
6507823 | Nel | Jan 2003 | B1 |
6529956 | Smith et al. | Mar 2003 | B1 |
6536659 | Hauser et al. | Mar 2003 | B1 |
6542933 | Durst, Jr. et al. | Apr 2003 | B1 |
6550672 | Tracy et al. | Apr 2003 | B1 |
6575361 | Graves et al. | Jun 2003 | B1 |
6581827 | Welton | Jun 2003 | B2 |
6591098 | Shieh et al. | Jul 2003 | B1 |
6594640 | Postrel | Jul 2003 | B1 |
6594644 | Dusen | Jul 2003 | B1 |
6609113 | O'Leary et al. | Aug 2003 | B1 |
6615189 | Phillips et al. | Sep 2003 | B1 |
6615190 | Slater | Sep 2003 | B1 |
6622015 | Himmel et al. | Sep 2003 | B1 |
6636833 | Flitcroft et al. | Oct 2003 | B1 |
6648222 | McDonald et al. | Nov 2003 | B2 |
6651885 | Arias | Nov 2003 | B1 |
6659259 | Knox et al. | Dec 2003 | B2 |
6678664 | Ganesan | Jan 2004 | B1 |
6684269 | Wagner | Jan 2004 | B2 |
6705520 | Pitroda et al. | Mar 2004 | B1 |
6745022 | Knox | Jun 2004 | B2 |
6769607 | Pitroda et al. | Aug 2004 | B1 |
6805289 | Noriega et al. | Oct 2004 | B2 |
6807410 | Pailles et al. | Oct 2004 | B1 |
6819219 | Bolle et al. | Nov 2004 | B1 |
6827260 | Stoutenburg et al. | Dec 2004 | B2 |
6829596 | Frazee | Dec 2004 | B1 |
6836765 | Sussman | Dec 2004 | B1 |
6836962 | Khandros et al. | Jan 2005 | B2 |
6839692 | Carrott et al. | Jan 2005 | B2 |
6839744 | Kloba et al. | Jan 2005 | B1 |
6848613 | Nielsen et al. | Feb 2005 | B2 |
6856974 | Ganesan et al. | Feb 2005 | B1 |
6868391 | Hultgren | Mar 2005 | B1 |
6882984 | Boyle et al. | Apr 2005 | B1 |
6915277 | Manchester et al. | Jul 2005 | B1 |
6918537 | Graves et al. | Jul 2005 | B2 |
6925439 | Pitroda | Aug 2005 | B1 |
6932268 | McCoy et al. | Aug 2005 | B1 |
6934529 | Bagoren et al. | Aug 2005 | B2 |
6934689 | Ritter et al. | Aug 2005 | B1 |
6941270 | Hannula | Sep 2005 | B1 |
6948063 | Ganesan et al. | Sep 2005 | B1 |
6961412 | Ruckart et al. | Nov 2005 | B2 |
6965866 | Klein | Nov 2005 | B2 |
6975937 | Kantarjiev et al. | Dec 2005 | B1 |
6988657 | Singer et al. | Jan 2006 | B1 |
6993510 | Guy et al. | Jan 2006 | B2 |
7014107 | Singer et al. | Mar 2006 | B2 |
7016863 | Kamakura et al. | Mar 2006 | B1 |
7024174 | Nagy et al. | Apr 2006 | B2 |
7024396 | Woodward | Apr 2006 | B2 |
7054842 | James et al. | May 2006 | B2 |
7069248 | Huber | Jun 2006 | B2 |
7072854 | Loeser | Jul 2006 | B2 |
7072864 | Brake, Jr. et al. | Jul 2006 | B2 |
7083084 | Graves et al. | Aug 2006 | B2 |
7085931 | Smith et al. | Aug 2006 | B1 |
7086584 | Stoutenburg et al. | Aug 2006 | B2 |
7093761 | Smith et al. | Aug 2006 | B2 |
7117227 | Call | Oct 2006 | B2 |
7128274 | Kelley et al. | Oct 2006 | B2 |
7130817 | Karas et al. | Oct 2006 | B2 |
7131582 | Welton | Nov 2006 | B2 |
7143055 | Perkowski | Nov 2006 | B1 |
7162440 | Koons | Jan 2007 | B2 |
7165052 | Diveley et al. | Jan 2007 | B2 |
7182252 | Cooper et al. | Feb 2007 | B1 |
7194438 | Sovio et al. | Mar 2007 | B2 |
7209889 | Whitfield | Apr 2007 | B1 |
7209890 | Peon et al. | Apr 2007 | B1 |
7216092 | Weber et al. | May 2007 | B1 |
7222101 | Bishop et al. | May 2007 | B2 |
7229006 | Babbi et al. | Jun 2007 | B2 |
7229014 | Snyder | Jun 2007 | B1 |
7243839 | Beck et al. | Jul 2007 | B2 |
7249054 | Keil | Jul 2007 | B2 |
7249097 | Hutchison et al. | Jul 2007 | B2 |
7269256 | Rosen | Sep 2007 | B2 |
7292998 | Graves et al. | Nov 2007 | B2 |
7316350 | Algiene | Jan 2008 | B2 |
7328190 | Smith et al. | Feb 2008 | B2 |
7333955 | Graves et al. | Feb 2008 | B2 |
7356327 | Cai et al. | Apr 2008 | B2 |
7363265 | Horgan | Apr 2008 | B2 |
7370012 | Kams et al. | May 2008 | B2 |
7376431 | Niedermeyer | May 2008 | B2 |
7383226 | Kight et al. | Jun 2008 | B2 |
7398248 | Phillips et al. | Jul 2008 | B2 |
7400883 | Rivers et al. | Jul 2008 | B2 |
7415617 | Ginter et al. | Aug 2008 | B2 |
7437328 | Graves et al. | Oct 2008 | B2 |
7494417 | Walker et al. | Feb 2009 | B2 |
7519543 | Ota et al. | Apr 2009 | B2 |
7536349 | Mik et al. | May 2009 | B1 |
7566000 | Agostino et al. | Jul 2009 | B2 |
7590557 | Harrison et al. | Sep 2009 | B2 |
7631803 | Peyret et al. | Dec 2009 | B2 |
7650308 | Nguyen et al. | Jan 2010 | B2 |
7702542 | Aslanian, Jr. | Apr 2010 | B2 |
7711598 | Perkowski | May 2010 | B2 |
7725326 | Tracy et al. | May 2010 | B1 |
7735724 | Fujita et al. | Jun 2010 | B2 |
7757944 | Cline et al. | Jul 2010 | B2 |
7774209 | James et al. | Aug 2010 | B2 |
7840437 | Lewis | Nov 2010 | B2 |
7848948 | Perkowski et al. | Dec 2010 | B2 |
7866548 | Reed et al. | Jan 2011 | B2 |
7904333 | Perkowski | Mar 2011 | B1 |
7905399 | Barnes et al. | Mar 2011 | B2 |
7917386 | Christensen | Mar 2011 | B2 |
7940333 | Suzuki | May 2011 | B2 |
7941373 | Chang et al. | May 2011 | B1 |
7959076 | Hopkins, III | Jun 2011 | B1 |
8046268 | Hunt | Oct 2011 | B2 |
8060413 | Castell et al. | Nov 2011 | B2 |
8103520 | Mueller et al. | Jan 2012 | B2 |
8109436 | Hopkins, III | Feb 2012 | B1 |
8195568 | Singhal | Jun 2012 | B2 |
8332323 | Stals et al. | Dec 2012 | B2 |
8355982 | Hazel et al. | Jan 2013 | B2 |
8396758 | Paradise et al. | Mar 2013 | B2 |
8509814 | Parker | Aug 2013 | B1 |
8577735 | Wilen et al. | Nov 2013 | B2 |
8636203 | Patterson et al. | Jan 2014 | B1 |
8662387 | Geller et al. | Mar 2014 | B1 |
8751298 | Giordano et al. | Jun 2014 | B1 |
8768834 | Zacarias et al. | Jul 2014 | B2 |
9098190 | Zhou et al. | Aug 2015 | B2 |
9483786 | Glass et al. | Nov 2016 | B2 |
9672687 | Cage et al. | Jun 2017 | B2 |
20010001321 | Resnick et al. | May 2001 | A1 |
20010001856 | Gould et al. | May 2001 | A1 |
20010005840 | Verkama | Jun 2001 | A1 |
20010007983 | Lee | Jul 2001 | A1 |
20010011248 | Himmel et al. | Aug 2001 | A1 |
20010032878 | Tsiounis et al. | Oct 2001 | A1 |
20010034707 | Sakaguchi | Oct 2001 | A1 |
20010037264 | Husemann et al. | Nov 2001 | A1 |
20010042784 | Fite et al. | Nov 2001 | A1 |
20010044776 | Kight et al. | Nov 2001 | A1 |
20010056410 | Ishigaki | Dec 2001 | A1 |
20020002535 | Kitchen et al. | Jan 2002 | A1 |
20020010627 | Lerat | Jan 2002 | A1 |
20020010677 | Kitchen et al. | Jan 2002 | A1 |
20020013768 | Ganesan | Jan 2002 | A1 |
20020019809 | Kitchen et al. | Feb 2002 | A1 |
20020022472 | Watler et al. | Feb 2002 | A1 |
20020046165 | Kitchen et al. | Apr 2002 | A1 |
20020046166 | Kitchen et al. | Apr 2002 | A1 |
20020046167 | Kitchen et al. | Apr 2002 | A1 |
20020046168 | Kitchen et al. | Apr 2002 | A1 |
20020049672 | Kitchen et al. | Apr 2002 | A1 |
20020052840 | Kitchen et al. | May 2002 | A1 |
20020052841 | Guthrie et al. | May 2002 | A1 |
20020060243 | Janiak et al. | May 2002 | A1 |
20020062249 | Iannacci | May 2002 | A1 |
20020062282 | Kight et al. | May 2002 | A1 |
20020065713 | Awada et al. | May 2002 | A1 |
20020065773 | Kight et al. | May 2002 | A1 |
20020065774 | Young et al. | May 2002 | A1 |
20020077076 | Suryanarayana et al. | Jun 2002 | A1 |
20020077993 | Immonen et al. | Jun 2002 | A1 |
20020088855 | Hodes | Jul 2002 | A1 |
20020091573 | Hodes | Jul 2002 | A1 |
20020101966 | Nelson | Aug 2002 | A1 |
20020107791 | Nobrega et al. | Aug 2002 | A1 |
20020111906 | Garrison et al. | Aug 2002 | A1 |
20020115424 | Bagoren et al. | Aug 2002 | A1 |
20020116329 | Serbetcioglu et al. | Aug 2002 | A1 |
20020119767 | Fieldhouse et al. | Aug 2002 | A1 |
20020120571 | Maung et al. | Aug 2002 | A1 |
20020128968 | Kitchen et al. | Sep 2002 | A1 |
20020138450 | Kremer | Sep 2002 | A1 |
20020138573 | Saguy | Sep 2002 | A1 |
20020152123 | Giordano et al. | Oct 2002 | A1 |
20020152160 | Allen-Rouman et al. | Oct 2002 | A1 |
20020152179 | Racov | Oct 2002 | A1 |
20020153414 | Stoutenburg et al. | Oct 2002 | A1 |
20020161631 | Banerjee et al. | Oct 2002 | A1 |
20020169713 | Chang et al. | Nov 2002 | A1 |
20020178062 | Wright et al. | Nov 2002 | A1 |
20020190123 | Anvekar et al. | Dec 2002 | A1 |
20020198722 | Yuschik | Dec 2002 | A1 |
20030001005 | Risafi | Jan 2003 | A1 |
20030004802 | Callegari | Jan 2003 | A1 |
20030004891 | Rensburg et al. | Jan 2003 | A1 |
20030004894 | Rowney et al. | Jan 2003 | A1 |
20030009382 | D'Arbeloff et al. | Jan 2003 | A1 |
20030023552 | Kight et al. | Jan 2003 | A1 |
20030028481 | Flitcroft et al. | Feb 2003 | A1 |
20030033246 | Slater | Feb 2003 | A1 |
20030055735 | Cameron et al. | Mar 2003 | A1 |
20030055782 | Slater | Mar 2003 | A1 |
20030070080 | Rosen | Apr 2003 | A1 |
20030074328 | Schiff et al. | Apr 2003 | A1 |
20030093366 | Halper et al. | May 2003 | A1 |
20030105672 | Epstein et al. | Jun 2003 | A1 |
20030105688 | Brown et al. | Jun 2003 | A1 |
20030115126 | Pitroda | Jun 2003 | A1 |
20030121967 | Goldberg et al. | Jul 2003 | A1 |
20030126079 | Roberson et al. | Jul 2003 | A1 |
20030141358 | Hudson et al. | Jul 2003 | A1 |
20030162565 | Al-Khaja | Aug 2003 | A1 |
20030163787 | Hay et al. | Aug 2003 | A1 |
20030172039 | Guy et al. | Sep 2003 | A1 |
20030191711 | Jamison et al. | Oct 2003 | A1 |
20030197059 | Tidball et al. | Oct 2003 | A1 |
20030200179 | Kwan | Oct 2003 | A1 |
20030200184 | Dominguez et al. | Oct 2003 | A1 |
20030212601 | Silva et al. | Nov 2003 | A1 |
20030218062 | Noriega et al. | Nov 2003 | A1 |
20030218066 | Fernandes et al. | Nov 2003 | A1 |
20030220884 | Choi et al. | Nov 2003 | A1 |
20030226042 | Fukushima | Dec 2003 | A1 |
20030229590 | Byrne et al. | Dec 2003 | A1 |
20030233317 | Judd | Dec 2003 | A1 |
20030233318 | King et al. | Dec 2003 | A1 |
20030234819 | Daly et al. | Dec 2003 | A1 |
20030236704 | Antonucci | Dec 2003 | A1 |
20040009760 | Laybourn et al. | Jan 2004 | A1 |
20040010462 | Moon et al. | Jan 2004 | A1 |
20040019564 | Goldthwaite et al. | Jan 2004 | A1 |
20040019568 | Moenickheim et al. | Jan 2004 | A1 |
20040029569 | Khan et al. | Feb 2004 | A1 |
20040046035 | Davila et al. | Mar 2004 | A1 |
20040049456 | Dreyer | Mar 2004 | A1 |
20040049458 | Kunugi et al. | Mar 2004 | A1 |
20040054587 | Dev et al. | Mar 2004 | A1 |
20040059671 | Nozaki et al. | Mar 2004 | A1 |
20040064409 | Kight et al. | Apr 2004 | A1 |
20040068446 | Do et al. | Apr 2004 | A1 |
20040068448 | Kim | Apr 2004 | A1 |
20040078327 | Frazier et al. | Apr 2004 | A1 |
20040078332 | Ferguson et al. | Apr 2004 | A1 |
20040083170 | Bam et al. | Apr 2004 | A1 |
20040083171 | Kight et al. | Apr 2004 | A1 |
20040093305 | Kight et al. | May 2004 | A1 |
20040094624 | Fernandes et al. | May 2004 | A1 |
20040107170 | Labrou et al. | Jun 2004 | A1 |
20040114766 | Hileman et al. | Jun 2004 | A1 |
20040117302 | Weichert et al. | Jun 2004 | A1 |
20040118914 | Smith et al. | Jun 2004 | A1 |
20040128197 | Bam et al. | Jul 2004 | A1 |
20040139005 | Ganesan | Jul 2004 | A1 |
20040159700 | Khan et al. | Aug 2004 | A1 |
20040162058 | Mottes | Aug 2004 | A1 |
20040167853 | Sharma | Aug 2004 | A1 |
20040181463 | Goldthwaite et al. | Sep 2004 | A1 |
20040185881 | Lee et al. | Sep 2004 | A1 |
20040199431 | Ganesan et al. | Oct 2004 | A1 |
20040199474 | Ritter | Oct 2004 | A1 |
20040205023 | Hafer et al. | Oct 2004 | A1 |
20040205138 | Friedman et al. | Oct 2004 | A1 |
20040210449 | Breck et al. | Oct 2004 | A1 |
20040215560 | Amalraj et al. | Oct 2004 | A1 |
20040215564 | Lawlor et al. | Oct 2004 | A1 |
20040215573 | Teutenberg et al. | Oct 2004 | A1 |
20040224660 | Anderson | Nov 2004 | A1 |
20040225560 | Lewis et al. | Nov 2004 | A1 |
20040230489 | Goldthwaite et al. | Nov 2004 | A1 |
20040232225 | Bishop et al. | Nov 2004 | A1 |
20040242208 | Teicher | Dec 2004 | A1 |
20040243490 | Murto et al. | Dec 2004 | A1 |
20040249710 | Smith et al. | Dec 2004 | A1 |
20040249766 | Ganesan et al. | Dec 2004 | A1 |
20040267663 | Karns et al. | Dec 2004 | A1 |
20040267664 | Nam et al. | Dec 2004 | A1 |
20040267665 | Nam et al. | Dec 2004 | A1 |
20050001027 | Bahar | Jan 2005 | A1 |
20050015388 | Dasgupta et al. | Jan 2005 | A1 |
20050021457 | Johnson et al. | Jan 2005 | A1 |
20050027624 | Cai | Feb 2005 | A1 |
20050027655 | Sharma et al. | Feb 2005 | A1 |
20050033645 | DuPhily | Feb 2005 | A1 |
20050051619 | Graves et al. | Mar 2005 | A1 |
20050060261 | Remington et al. | Mar 2005 | A1 |
20050061872 | Paschini et al. | Mar 2005 | A1 |
20050065876 | Kumar | Mar 2005 | A1 |
20050071179 | Peters et al. | Mar 2005 | A1 |
20050071269 | Peters | Mar 2005 | A1 |
20050075958 | Gonzalez | Apr 2005 | A1 |
20050075975 | Rosner et al. | Apr 2005 | A1 |
20050079863 | Macaluso | Apr 2005 | A1 |
20050080634 | Kanniainen et al. | Apr 2005 | A1 |
20050080727 | Postrel | Apr 2005 | A1 |
20050086164 | Kim et al. | Apr 2005 | A1 |
20050086168 | Alvarez et al. | Apr 2005 | A1 |
20050096981 | Shimada | May 2005 | A1 |
20050097038 | Yu et al. | May 2005 | A1 |
20050103839 | Hewel | May 2005 | A1 |
20050107068 | Smith et al. | May 2005 | A1 |
20050109835 | Jacoby et al. | May 2005 | A1 |
20050116028 | Cohen et al. | Jun 2005 | A1 |
20050125343 | Mendelovich | Jun 2005 | A1 |
20050125348 | Fulton et al. | Jun 2005 | A1 |
20050127169 | Foss | Jun 2005 | A1 |
20050137978 | Ganesan et al. | Jun 2005 | A1 |
20050143051 | Park | Jun 2005 | A1 |
20050154644 | Deakin et al. | Jul 2005 | A1 |
20050174975 | Mgrdechian et al. | Aug 2005 | A1 |
20050177437 | Ferrier | Aug 2005 | A1 |
20050177517 | Leung et al. | Aug 2005 | A1 |
20050182714 | Nel | Aug 2005 | A1 |
20050182720 | Willard et al. | Aug 2005 | A1 |
20050184145 | Law et al. | Aug 2005 | A1 |
20050187873 | Labrou et al. | Aug 2005 | A1 |
20050199709 | Linlor | Sep 2005 | A1 |
20050203835 | Nhaissi et al. | Sep 2005 | A1 |
20050203844 | Ferguson et al. | Sep 2005 | A1 |
20050209965 | Ganesan | Sep 2005 | A1 |
20050222925 | Jamieson | Oct 2005 | A1 |
20050222961 | Staib et al. | Oct 2005 | A1 |
20050228717 | Gusler et al. | Oct 2005 | A1 |
20050247777 | Pitroda | Nov 2005 | A1 |
20050259589 | Rozmovits et al. | Nov 2005 | A1 |
20050261968 | Randall et al. | Nov 2005 | A1 |
20050262017 | Kawase et al. | Nov 2005 | A1 |
20050269401 | Spitzer et al. | Dec 2005 | A1 |
20050269402 | Spitzer et al. | Dec 2005 | A1 |
20050274793 | Cantini et al. | Dec 2005 | A1 |
20060000900 | Fernandes et al. | Jan 2006 | A1 |
20060004631 | Roberts et al. | Jan 2006 | A1 |
20060004656 | Lee | Jan 2006 | A1 |
20060006226 | Fitzgerald et al. | Jan 2006 | A1 |
20060023856 | Welton | Feb 2006 | A1 |
20060026070 | Sun | Feb 2006 | A1 |
20060037835 | Doran | Feb 2006 | A1 |
20060041470 | Filho et al. | Feb 2006 | A1 |
20060053056 | Alspach-Goss et al. | Mar 2006 | A1 |
20060058011 | Vanska et al. | Mar 2006 | A1 |
20060074767 | Fortney et al. | Apr 2006 | A1 |
20060080232 | Epps | Apr 2006 | A1 |
20060085310 | Mylet et al. | Apr 2006 | A1 |
20060089160 | Othmer | Apr 2006 | A1 |
20060089893 | Joseph et al. | Apr 2006 | A1 |
20060113376 | Reed et al. | Jun 2006 | A1 |
20060116892 | Grimes et al. | Jun 2006 | A1 |
20060136334 | Atkinson et al. | Jun 2006 | A1 |
20060136901 | Nichols | Jun 2006 | A1 |
20060161490 | Chakiris et al. | Jul 2006 | A1 |
20060163343 | Changryeol | Jul 2006 | A1 |
20060167744 | Yoo | Jul 2006 | A1 |
20060206436 | James et al. | Sep 2006 | A1 |
20060207856 | Dean et al. | Sep 2006 | A1 |
20060235754 | Walker et al. | Oct 2006 | A1 |
20060253320 | Heywood | Nov 2006 | A1 |
20060255125 | Jennings et al. | Nov 2006 | A1 |
20070017976 | Peyret et al. | Jan 2007 | A1 |
20070021969 | Homeier-Beals | Jan 2007 | A1 |
20070030824 | Ribaudo et al. | Feb 2007 | A1 |
20070038577 | Werner et al. | Feb 2007 | A1 |
20070043682 | Drapkin et al. | Feb 2007 | A1 |
20070055785 | Stevens | Mar 2007 | A1 |
20070063024 | Guillot | Mar 2007 | A1 |
20070100761 | Dillon | May 2007 | A1 |
20070108269 | Benco et al. | May 2007 | A1 |
20070114274 | Gibbs et al. | May 2007 | A1 |
20070118478 | Graves et al. | May 2007 | A1 |
20070125838 | Law et al. | Jun 2007 | A1 |
20070130085 | Zhu | Jun 2007 | A1 |
20070156436 | Fisher et al. | Jul 2007 | A1 |
20070162337 | Hawkins et al. | Jul 2007 | A1 |
20070175984 | Khandaker et al. | Aug 2007 | A1 |
20070192182 | Monaco et al. | Aug 2007 | A1 |
20070198347 | Muldoon | Aug 2007 | A1 |
20070208618 | Paintin et al. | Sep 2007 | A1 |
20070233615 | Tumminaro | Oct 2007 | A1 |
20070257767 | Beeson | Nov 2007 | A1 |
20070262140 | Long | Nov 2007 | A1 |
20070265872 | Robinson et al. | Nov 2007 | A1 |
20070284434 | Fletcher | Dec 2007 | A1 |
20080006685 | Rackley, III et al. | Jan 2008 | A1 |
20080010190 | Rackley, III et al. | Jan 2008 | A1 |
20080010191 | Rackley, III et al. | Jan 2008 | A1 |
20080010192 | Rackley, III et al. | Jan 2008 | A1 |
20080010193 | Rackley, III et al. | Jan 2008 | A1 |
20080010196 | Rackley, III et al. | Jan 2008 | A1 |
20080010204 | Rackley, III et al. | Jan 2008 | A1 |
20080010215 | Rackley, III et al. | Jan 2008 | A1 |
20080028395 | Motta et al. | Jan 2008 | A1 |
20080033817 | Billmaier et al. | Feb 2008 | A1 |
20080040265 | Rackley, III et al. | Feb 2008 | A1 |
20080041938 | Wise | Feb 2008 | A1 |
20080046366 | Bemmel et al. | Feb 2008 | A1 |
20080052164 | Abifaker | Feb 2008 | A1 |
20080052169 | O'Shea et al. | Feb 2008 | A1 |
20080059318 | Packes et al. | Mar 2008 | A1 |
20080070690 | Luchene et al. | Mar 2008 | A1 |
20080071620 | Lowe | Mar 2008 | A1 |
20080078831 | Johnson et al. | Apr 2008 | A1 |
20080091545 | Jennings et al. | Apr 2008 | A1 |
20080097844 | Hsu et al. | Apr 2008 | A1 |
20080097851 | Bemmel et al. | Apr 2008 | A1 |
20080103972 | Lanc | May 2008 | A1 |
20080114699 | Yuan et al. | May 2008 | A1 |
20080126145 | Rackley, III et al. | May 2008 | A1 |
20080133351 | White et al. | Jun 2008 | A1 |
20080172306 | Schorr et al. | Jul 2008 | A1 |
20080172331 | Graves et al. | Jul 2008 | A1 |
20080179395 | Dixon et al. | Jul 2008 | A1 |
20080228597 | Sondles | Sep 2008 | A1 |
20080235095 | Oles et al. | Sep 2008 | A1 |
20080255942 | Craft | Oct 2008 | A1 |
20080273630 | Mege et al. | Nov 2008 | A1 |
20080290987 | Li | Nov 2008 | A1 |
20080319868 | Briscoe et al. | Dec 2008 | A1 |
20090001159 | James et al. | Jan 2009 | A1 |
20090006116 | Baker et al. | Jan 2009 | A1 |
20090030789 | Mashinsky | Jan 2009 | A1 |
20090037326 | Chitti et al. | Feb 2009 | A1 |
20090055296 | Nelsen | Feb 2009 | A1 |
20090076896 | DeWitt et al. | Mar 2009 | A1 |
20090106115 | James et al. | Apr 2009 | A1 |
20090111378 | Sheynman et al. | Apr 2009 | A1 |
20090112709 | Barhydt et al. | Apr 2009 | A1 |
20090144161 | Fisher | Jun 2009 | A1 |
20090157554 | Hobson et al. | Jun 2009 | A1 |
20090164329 | Bishop et al. | Jun 2009 | A1 |
20090171739 | De et al. | Jul 2009 | A1 |
20090171804 | Lee et al. | Jul 2009 | A1 |
20090173782 | Muscato | Jul 2009 | A1 |
20090173784 | Yang | Jul 2009 | A1 |
20090187491 | Bull et al. | Jul 2009 | A1 |
20090192904 | Patterson et al. | Jul 2009 | A1 |
20090192928 | Abifaker | Jul 2009 | A1 |
20090247131 | Champion et al. | Oct 2009 | A1 |
20090254453 | Sanguinetti et al. | Oct 2009 | A1 |
20090281915 | Deakin et al. | Nov 2009 | A1 |
20090281941 | Worth | Nov 2009 | A1 |
20090281951 | Shakkarwar | Nov 2009 | A1 |
20090287558 | Seth et al. | Nov 2009 | A1 |
20090298427 | Wilkinson et al. | Dec 2009 | A1 |
20090327121 | Carroll et al. | Dec 2009 | A1 |
20100005025 | Kumar et al. | Jan 2010 | A1 |
20100008535 | Abulafia et al. | Jan 2010 | A1 |
20100010906 | Grecia | Jan 2010 | A1 |
20100041368 | Kumar | Feb 2010 | A1 |
20100042471 | Chang et al. | Feb 2010 | A1 |
20100063906 | Nelsen et al. | Mar 2010 | A1 |
20100076833 | Nelsen | Mar 2010 | A1 |
20100082487 | Nelsen | Apr 2010 | A1 |
20100082490 | Rosenblatt et al. | Apr 2010 | A1 |
20100088188 | Kumar et al. | Apr 2010 | A1 |
20100097180 | Cardullo | Apr 2010 | A1 |
20100130172 | Vendrow et al. | May 2010 | A1 |
20100131415 | Sartipi | May 2010 | A1 |
20100174993 | Pennington et al. | Jul 2010 | A1 |
20100175287 | Gupta et al. | Jul 2010 | A1 |
20100185505 | Sprogoe et al. | Jul 2010 | A1 |
20100205063 | Mersky | Aug 2010 | A1 |
20100280921 | Stone et al. | Nov 2010 | A1 |
20100293536 | Nikitin et al. | Nov 2010 | A1 |
20100299194 | Snyder et al. | Nov 2010 | A1 |
20100299266 | Catania et al. | Nov 2010 | A1 |
20100304852 | Szrek et al. | Dec 2010 | A1 |
20110087592 | Veen et al. | Apr 2011 | A1 |
20110091092 | Nepomniachtchi et al. | Apr 2011 | A1 |
20110106698 | Isaacson et al. | May 2011 | A1 |
20110125607 | Wilen | May 2011 | A1 |
20110145044 | Nelsen et al. | Jun 2011 | A1 |
20110161226 | Courtion et al. | Jun 2011 | A1 |
20110173083 | Reed et al. | Jul 2011 | A1 |
20110202419 | Mamdani et al. | Aug 2011 | A1 |
20110234514 | Gothard | Sep 2011 | A1 |
20110246284 | Chaikin et al. | Oct 2011 | A1 |
20110251962 | Hruska | Oct 2011 | A1 |
20120004769 | Hallenbeck et al. | Jan 2012 | A1 |
20120099780 | Smith et al. | Apr 2012 | A1 |
20120136780 | El-Awady et al. | May 2012 | A1 |
20120203572 | Christensen | Aug 2012 | A1 |
20120209688 | Lamothe et al. | Aug 2012 | A1 |
20120234911 | Yankovich et al. | Sep 2012 | A1 |
20120271689 | Etheredge et al. | Oct 2012 | A1 |
20120284185 | Mettler et al. | Nov 2012 | A1 |
20130073388 | Heath | Mar 2013 | A1 |
20130290121 | Simakov et al. | Oct 2013 | A1 |
20130304561 | Warner et al. | Nov 2013 | A1 |
20140006268 | Roberts et al. | Jan 2014 | A1 |
20140019238 | Blatchley et al. | Jan 2014 | A1 |
20150100418 | Gangi | Apr 2015 | A1 |
20150278845 | Sorem et al. | Oct 2015 | A1 |
20160162882 | McClung, III | Jun 2016 | A1 |
20170076293 | Cage et al. | Mar 2017 | A1 |
Number | Date | Country |
---|---|---|
0950968 | May 2004 | EP |
1519332 | Mar 2005 | EP |
2128809 | Dec 2009 | EP |
2002189963 | Jul 2002 | JP |
2002318951 | Oct 2002 | JP |
2003208541 | Jul 2003 | JP |
20010106187 | Nov 2001 | KR |
20040028487 | Apr 2004 | KR |
20040052531 | Jun 2004 | KR |
1020040052502 | Jun 2004 | KR |
20040069294 | Aug 2004 | KR |
20050118609 | Dec 2005 | KR |
20090123444 | Dec 2009 | KR |
2004012118 | Feb 2004 | WO |
2005111882 | Nov 2005 | WO |
2008005018 | Jan 2010 | WO |
2013078499 | Jun 2013 | WO |
Entry |
---|
Eazel, William, “Paypal intros SMS Payments,” http://www.v3co.uk/articles/print/2152694, vnunet.com, Mar. 24, 2006, 1 page. |
International Search Report of PCT/US 13/23945, dated Mar. 29, 2013; 2 pages. |
ISA European Patent Office, Search Report of EP09812328.4, dated Jul. 4, 2012, Germany, 6 pages. |
ISA Korea, International Search Report of PCT/US2009/056118, dated Apr. 19, 2010, 3 pages. |
ISA Korea, International Search Report of PCT/US2009/058111, dated May 26, 2010, 3 pages. |
ISA Korean Intellectual Property Office, International Search Report of PCT/US2010/060875, dated Jul. 29, 2011, 10 pages. |
ISA United States Patent and Trademark Office, International Search Report of PCT/US2008/073910, dated Nov. 10, 2008. |
Nelsen, David A., “Systems and Methods to Manage and Control Use of a Virtual Card,” U.S. Appl. No. 13/158,349, filed Jun. 10, 2011, 62 pages. |
Number | Date | Country | |
---|---|---|---|
20190188688 A1 | Jun 2019 | US |
Number | Date | Country | |
---|---|---|---|
61818789 | May 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13946679 | Jul 2013 | US |
Child | 16284150 | US |