1. Field of the Invention
The present invention relates to transaction cards and, more particularly, to providing multiple monetary transaction cards in a single package and enabling the multiple monetary transaction cards to be activated substantially simultaneously.
2. Description of the Related Art
Monetary transaction cards generally include smart cards, credit cards, debit cards, automatic teller machine (ATM) cards, identification (ID) cards, and pre-paid cards such as gift cards. Typically, monetary transaction cards are of a standard credit card size, or a size of a CR-80 card. The monetary transaction cards generally include a magnetic stripe which includes a number of tracks encoded thereon. Information associated with the monetary transaction cards is stored on the tracks.
Monetary transaction cards that are gift cards or other pre-paid cards are often attached to carrier cards, and displayed at retail locations. Carrier assemblies often include transaction cards that are mounted to carrier cards using an adhesive. Such carrier assemblies may include openings which enable the carrier assemblies to be hung on a rack for display purposes.
To activate a transaction card that is a part of a carrier assembly, a purchaser may remove the carrier assembly from a display rack, and bring the carrier assembly to a point-of-sale (POS). When such a purchaser wishes to purchase or otherwise obtain multiple transaction cards, he or she selects individual transaction cards which are then individually activated, e.g., using a computing system at a POS. When transaction cards are to be activated, activating the transaction card one-by-one may be inefficient.
Therefore, what is needed is a method and an apparatus for facilitating the activation of more than one transaction card using a single POS transaction. That is, what is desired is a method and an apparatus for activating multiple transaction cards substantially simultaneously and efficiently.
The present invention pertains to providing and facilitating activation of multiple transaction cards (e.g., pre-paid cards). The present invention may be implemented in numerous ways, including, but not limited to, as a method, system, device, or apparatus (including computer program code). Exemplary embodiments of the present invention are discussed below.
According to one aspect of the present invention, a method for forming a carrier package arrangement includes obtaining a plurality of transaction cards, obtaining a first parent activation code, and associating the first parent activation code with the plurality of transaction cards. The method also includes packing the plurality of transaction cards in the carrier package arrangement, and providing the first parent activation code so as to be on or accessible from the carrier package arrangement. The plurality of transaction cards is activated using the first parent activation code.
According to another aspect of the present invention, a method of activating a plurality of transaction cards included in a card package that has a package activation code includes obtaining information associated with the package activation code. The information is used to identify the transaction cards as being mapped to the package activation code. A determination is made as to whether each transaction card of is in an unactivated state. If each transaction card is in an unactivated state, the package activation code is used to transition each transaction card from an unactivated state to an activated state.
In accordance with still another aspect of the present invention, a carrier package arrangement includes a carrier card arrangement, a tray, and a plurality of transaction cards. The transaction cards are mounted on the tray, and the tray is supported within the carrier card arrangement. The transaction cards are arranged to be transitioned from an unactivated state to an activated state using a first activation code associated with the carrier package arrangement.
According to yet another aspect of the present invention, a method for forming carrier package arrangements includes obtaining a plurality of transaction cards. The transaction cards include a first transaction card having a first card activation code and a second transaction card having a second card activation code. The method also includes obtaining a parent code file that specifies at least a first parent code and a second parent code. A first set of transaction cards is defined to include at least the first transaction card. The first parent code is mapped to the first set of transaction cards such that the first parent code is mapped to at least the first card activation code. The method further includes assembling the first set of transaction cards into a first carrier package arrangement, and providing the first parent code on the first carrier package arrangement. The first set of transaction cards is arranged to be activated using the first parent code.
Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.
The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, in which:
Exemplary embodiments of the present invention are discussed below with reference to the various figures. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes, as the invention extends beyond these embodiments.
Providing multiple transaction cards, e.g., pre-paid cards such as gift cards, in a single package such that the transaction cards may substantially all be activated at one time increases the efficiency with which separate gift cards may be activated. By way of example, a package that contains multiple gift cards may be arranged such that a single activation code associated with the package may be used to activate all of the gift cards at the same time. When information relating to the single activation code, or the “package code,” is provided to an authentication and authorization system, the authentication and authorization system may cause all of the gift cards included in the package to be activated.
A multi-pack package of transaction cards may include multiple transaction cards that are mounted on a carrier card or a holder, or otherwise associated with a carrier card or a holder. The carrier card (or holder) and the multiple transaction cards may effectively form a carrier assembly. A single activation code or package code that allows the multiple transaction cards to be activated may be provided on the carrier card or holder.
The activation codes of the transactions cards included in a multi-pack package of transaction cards are identified as being associated with a package code that is associated with the multi-pack package. Hence, verifying or otherwise activating the package code generally causes the transaction cards to be activated. In other words, the activation of a package code associated with a multi-pack package of transaction cards effectively causes each of the transaction cards to be verified and activated.
A package or parent code may, in one embodiment, be associated with a set of transaction or child cards that is to be part of a multi-pack package substantially only after the set of transaction cards is identified during a multi-pack package assembly process. By associating a set of transaction cards with a package card after the set of transaction cards is identified during a multi-pack package assembly process, the assembly process may be facilitated. For example, the assembly process may be facilitated because the need to keep track of transaction cards from the time transaction cards are received at an assembly plant is reduced. Substantially eliminating the need to verify that the correct transaction cards remain together for subsequent packaging into a single multi-pack package increases the efficiency and flexibility with which the transaction cards may be processed, as substantially random transaction cards may be handled and associated with a package code relatively late in multi-pack package assembly process.
Referring initially to
Each transaction card 104a-c has an associated card activation code 108a-c, respectively. Card activation codes 108a-c are unique codes which enable their respective transaction cards 104a-c to be activated upon activation of package activation code 112. In other words, because package activation code 112 typically includes or otherwise identifies information 116 which identifies card activation codes 104a-c with which package activation code 112 is associated, when package activation code 112 is activated, transaction cards 104a-c are activated. As such, the verification and/or activation of package activation code 112 is arranged to enable each transaction card 104a-c to be activated.
After the package code is scanned, the package code is provided in step 209 from the point-of-sale to an activation and authentication system. That is, information that is obtained from the package code is sent or otherwise transmitted to the activation and authentication system such that the activation and authentication system may activate the individual transaction cards that are associated with the package code.
A determination is made in step 213 as to whether the activation and authentication system has verified every transaction card in the multi-pack package for activation. In other words, it is determined in step 213 whether each transaction card included in the multi-pack package has been successfully activated using the package code. If it is determined that the multi-pack package is not activated, then process flow proceeds to step 217 in which an indication is received that the transaction cards in the multi-pack package may not be activated. Once the indication that the transaction cards may not be activated is received, the process of activating the multi-pack package is completed.
Alternatively, if it is determined in step 213 that every card in the multi-pack package is verified for activation, the indication is that each transaction card included in the multi-pack package has been activated. Accordingly, in step 221, an indication is obtained from the activation and authentication system which indicates that each transaction card in the multi-pack package is activated. Such an indication may indicate that each transaction card has been transitioned from an unactivated state to an activated state using the package code. After the indication is obtained, the transaction cards are effectively activated and, hence, ready for use in step 225. The process of activating the multi-pack package of transaction cards that has a single package code is completed upon allowing the activated transaction cards to be used.
When an activation and authentication system obtains a package code for a multi-pack package of transaction cards, the activation and authentication system may identify the individual card activation codes associated with the package code, determine whether the individual card activation codes are valid, and activate the transaction cards as appropriate. The activation and authentication system may be associated with, for example, an originator or a retailer of the transaction cards. In one embodiment, activation and authentication system may be an overall computing system associated with a retailer which provides cash value, goods, and/or services when a transaction card is activated and/or redeemed. The package code may be a code, e.g., a 16-digit alphanumeric code, that is specific to a retailer.
In step 309, card activation codes for each transaction card associated with the package code are identified. The card activation codes may be identified using a data structure, e.g., a list, which associates the package code with card activation codes of the transaction cards. In other words, card activation codes may be identified by determining which card activation codes are effectively mapped to the package code.
Once the card activation codes are identified, it is then identified or otherwise determined in step 313 whether each of the card activation codes are valid. Such an identification may include, but is not limited to including, identifying whether the transaction cards associated with each of the card activation codes have yet to be activated. A determination is made in step 317 as to whether substantially all card activation codes are valid. In other words, it is effectively ascertained whether each transaction card in the multi-pack package of transaction cards is valid.
If the determination in step 317 is that substantially all card activation codes are valid, the indication is that each transaction card in the multi-pack package of transaction cards is valid. Accordingly, in step 321, substantially all activation codes associated with the package code assigned to the multi-pack package of transaction codes are activated. In general, any suitable method for activating or validating the activation codes may be used. By way of example, a flag associated with an entry in a data structure stored by an activation system may be set to indicate that a particular activation code and, hence, an associated transaction card is activated.
After the activation codes associated with the package code are activated, process flow proceeds to step 325 in which the activation system provides an indication arranged to indicate that the activation codes are activated. Such an indication may be provided by sending an activation message to the POS of a retailer, or the POS from which the package code was obtained in step 305. Upon providing an indication that the activation codes are activated, the process of activating a multi-pack package of transaction cards from the point-of-view of an activation system is completed.
Alternatively, if it is determined in step 317 that substantially all card activation codes are not valid, the implication is that at least one transaction card in the multi-pack package of transaction cards may not be activated. As such, the activation system provides an indication, e.g., to the POS from which the package code was obtained, that the package code is invalid in step 329, the process of activating a multi-pack package of transaction cards from the point-of-view of an activation system is terminated.
In one embodiment, a plurality of transaction cards is paired or otherwise associated with a package code substantially only after the plurality of transaction cards are identified. That is, until a set of transaction cards is identified for use in a multi-pack package of transaction cards, a package code is not associated with the multi-pack package of transaction cards. When an order to assemble a multi-pack package of transaction cards is received by an assembler, e.g., from an originator of the transaction cards, the order may generally include a list of package codes, but does not specify which transaction cards are to be associated with each package code. In other words, an association between a set of activation codes and a package code is generally not provided to an assembler.
A list of package codes for multi-pack packages of transaction cards is obtained in step 409. The list of parent codes, e.g., retailer-specific parent codes, may be provided in a “parent code” file which includes. One example of a parent code file will be described below with respect to
After the list of package codes is obtained, a first set of transaction cards or a first set of activation codes is identified in step 413. The parent code file can indicate the number and/or order of transaction cards to be included in the multi-pack packages. The first set of transaction cards may be any number of transaction cards, which each have a unique activation code, which are to be associated with a single multi-pack package of transaction cards. Once the first set of transaction cards is identified, a package code is selected from the list of package codes in step 417.
The selected package code is associated in step 421 with the set of transaction cards previously identified in step 413. It should be appreciated that prior to step 421, the selected package code for a multi-pack package of transaction cards is not mapped to a specific set of transaction cards and, hence, the activation codes of the transaction cards, that are to be included in the multi-pack package. Associating a package code with a set of transaction cards may include creating and/or updating a “mapping” file which is arranged to identify the activation codes of transaction cards that are associated with a specific package code. One suitable mapping file will be described below with reference to
Once the selected package code is associated with a set of transaction cards, a multi-pack package is created from the set of transaction cards and a carrier card in step 425. Creating a multi-pack package may include, but is not limited to including, using an adhesive to substantially secure each transaction card to the carrier card or a tray associated with the carrier card. After the multi-pack package is created, the selected package code is printed on the carrier card in step 429. It should be appreciated that although the selected package code is printed on the carrier card after the multi-pack package is created, the selected package code may instead be printed on the carrier card prior to creating the multi-pack package. Printing the selected package code on the carrier card may include verifying that the activation codes of the transaction cards which are part of the multi-pack package are those that were previously associated with the package code in step 421.
A determination is made in step 433 as to whether there are more transaction cards to process. In other words, it is determined whether more multi-pack packages are to be created. If the determination is that there are more transaction cards to process, then process flow returns to step 413 in which another set of transaction cards is identified.
Alternatively, if the determination is that there are no more transaction cards to process, then at least one multi-pack package of transaction cards is provided to an appropriate entity in step 437. Typically, each multi-pack package which has been created based on the list of package codes obtained in step 409 is provided to the appropriate entity. Providing a multi-pack package to an appropriate entity may include transporting the multi-pack package to the appropriate entity. In one embodiment, the appropriate entity may be an originator, e.g., a provider of the transaction cards, or a third-party retailer that will display and/or sell multi-pack packages.
Information is provided to an originator in step 441 to effectively inform the originator that at least one multi-pack package has been created. The information may include a mapping file which provides a mapping between each parent code and the transaction cards in each multi-pack package. Once the information is provided, the process of associating transaction cards and, hence, activation codes with a package is completed.
As previously mentioned, package codes may be provided, e.g., by a retailer to an external partner such as a multi-pack package assembler, in a package code file. With reference to
Header portion 524 includes a batch number 528 associated with parent codes 552a, 552b included in parent code list 548. Batch number 528 may generally be specified in any suitable format. By way of example, batch number 528 may be specified as a string of approximately twelve characters which may include a prefix and a number of digits. Header portion 524 also includes a number 532 of parent codes included in package code file 520, a face value 536 for multi-pack packages that are to be created using parent codes 552a, 552b, and a multi-pack size 540 which specifies a number of transaction cards to be included in each multi-pack package.
Package or parent code list 548 includes at least one parent code 552a, 552b. It should be appreciated that although two parent codes 552a, 552b are shown, package code list 548 may generally include any number of parent codes 552a, 552b. Parent codes 552a, 552b may generally be character strings of any suitable length. By way of example, parent codes 552a, 552b may include a prefix, a sequence number, and a checksum. In one embodiment, such a prefix may include approximately three characters, such a sequence number may include approximately eleven digits, and such a checksum may include approximately two digits.
Package code file 520 may be specified in any suitable format. In one embodiment, package code file 520 may be specified in a file format in which entries are separated by commas. For example, package code file 520 may list batch number 528, number 532 of parent codes, face value 536, size 540, part numbers 544, parent code 552a, and parent code 552b substantially all separated by commas. The part numbers 544 can identify the transaction cards to be included in the multi-pack packages. Also, the ordering of the part numbers 544 can signify the order of placement of the transaction cards within the multi-pack packages.
Upon receiving package code file 520, an external partner such as an assembler or packager may use package code file 520 to create multi-pack packages of transaction cards. In one embodiment, the external partner may create a mapping file which identifies associations between package or parent codes 552a, 552b and transaction cards mapped to package codes 552a, 552b. Referring next to
Header portion 556 includes a batch number 558 which identifies the batch of parent codes which was effectively processed to generate multi-pack packages. Header portion 556 also includes a number 560 of parent codes which is, typically, substantially the same as a number of multi-pack packages associated with batch number 558. A number 562 of activation or child codes identifies a total number of transaction cards used to create multi-pack packages associated with parent codes 560. A multi-pack size 564 and a face value 566 of each multi-pack package are also specified in header portion 556.
It should be appreciated that the contents of header portion 556 may vary widely. Information may be added and removed depending upon the requirements of a particular system within which mapping file 554 is generated and used. By way of example, in lieu of specifying a number 562 of activation codes or a “child count,” a number of activation codes associated with batch number 558 may be determined by substantially multiplying multi-pack size 564 by number 560 of parent codes.
Mapping data 570 may generally include any number of entries 572a-c. In general, mapping data 570 includes a number of entries 572a-c that is substantially equal to number 562 of activation codes. Each entry 572a-c corresponds to a transaction card or an activation code, and identifies the activation code, a parent code for the multi-pack package with which the activation code is associated, and an indication of a position of the transaction card relative to the multi-pack package. For example, if each multi-pack size 564 is “two,” thus effectively indicating that each parent code is associated with two activation codes, entry 572a may identify a first transaction card or activation code as being a first transaction card associated with a first parent code, entry 572b may identify a second transaction card as being a second transaction card associated with the first parent code, and entry 572c may identify a third transaction card as being a first transaction card associated with a second parent code. Each parent code and child code included in mapping data may include any number of characters, as for example a prefix, a unique sequence number, and a checksum.
A multi-pack package of transaction cards may be of substantially any size, and may include any number of transaction cards.
In one embodiment, transaction cards 680a-d may be supported on a sleeve or a tray (not shown) that is inserted within carrier card arrangement 678. Such a sleeve (not shown) will be discussed below with reference to
Similarly, the dimensions of carrier card arrangement 678 may also vary widely. By way of example, a height h 684 relative to a z-direction 688c and a width w 686 relative to an x-direction 688a of carrier card arrangement 678 may be widely varied. By way of example, height h 684 may be approximately six inches and width w 686 may be approximately four inches. Generally, height h 684 may be increased as appropriate to accommodate additional transaction cards 700a-d. Additionally, a thickness (not shown) relative to a y-direction 688b of carrier card arrangement 678 may also vary.
Carrier card arrangement 678 includes a relatively transparent window piece 698, e.g., a plastic piece, which protects transaction cards 680a-d while allowing front surfaces of transaction cards 689a-d to be viewed. Carrier card arrangement 678 may also include an opening 682 which allows multi-pack package 676 to be hung on a display rack, e.g., a display rack managed by a third-party retailer. It should be understood, however, that opening 682 may not be necessary in the event that multi-pack package 676 is not intended to be displayed on a display rack.
Back surface of carrier card arrangement 678 may include a flap or a “garage door” 694 which is arranged to be opened to facilitate the removal of transaction cards 680a-d that are positioned in a receptacle or a cavity (not shown) of carrier card arrangement 678. The inclusion of flap 694 also facilitates the inclusion of other elements, e.g., coupons or a bonus transaction card, in carrier card arrangement 678. In one embodiment, flap 694 is arranged to remain substantially attached to the back surface of carrier card arrangement 678 when opened to expose a cavity (not shown) in carrier card arrangement 678.
As previously mentioned, transaction cards 680a-d may be mounted on a sleeve or a tray (not shown) to form an overall assembly which is arranged to fit in a cavity (not shown) of carrier card arrangement 678. Mounting transaction cards 680a-d on a sleeve (not shown) using an adhesive material allows transaction cards 680a-d to be readily removed, and also readily inserted, within carrier card arrangement 678. With reference to
In general, the size and shape of sleeve 796 may vary based upon a variety of factors. Such factors include, but are not limited to including, the size of transaction cards 780a-d, the number of transaction cards 780a-d, and/or the size of a carrier card arrangement (not shown) within which sleeve 796 and transaction cards 780a-d are to be accommodated.
Although only a few embodiments of the present invention have been described, it should be understood that the present invention may be embodied in many other specific forms without departing from the spirit or the scope of the present invention. By way of example, a package code that may be a retailer-specific parent code has been described as being a 16-digit alphanumeric code. The package code, however, may generally be any suitable code, alphanumeric or otherwise, and is not limited to being a 16-digit alphanumeric code.
A package code file has been described as generally being generated by an originator or a retailer when multi-pack packages of transaction cards are to be created and sold, e.g., by a third-party retailer. Prior to providing a package code file to a packager, the retailer may define artwork to be displayed on transaction cards and on the multi-pack packages, define a denomination of the transaction cards to be included in the multi-pack packages, and define a number of transaction cards to be included in each multi-pack package. The retailer may also coordinate with a manufacturer of transaction cards to provide appropriate transaction cards to the packager. In one embodiment, the transaction cards and their associated child activation codes are provided to a packager separately from a package code file that includes parent activation codes. The parent activation codes may then be assigned to or otherwise associated with the child codes by the packager.
As mentioned above, the size of a transaction card may vary widely. For instance, a transaction card may be the size of a standard CR-80 card. Alternatively, a transaction card may be smaller than a CR-80 card, e.g., approximately two inches in height and approximate three inches in width as described above, or larger than a CR-80 transaction card.
Adhesive has been described as being suitable for mounting or otherwise securing transaction cards to a surface associated with a carrier card arrangement. In general, transaction cards may be substantially secured to a carrier card using any suitable method. For example, transaction cards may be secured to a carrier card by inserting transaction cards in slits or cuts that are made in the carrier card.
Displaying transaction cards in a fanned pattern on the surface of a carrier card, or such that the transaction cards may be viewed from a front surface of a carrier card is viewed, allows a purchaser to readily see each transaction card that he or she is purchasing when he purchases a multi-pack of transaction cards. However, transaction cards of a multi-pack are not limited to being displayed in a fanned pattern. For instance, transaction cards may be stacked one on top of the other such that substantially only a front surface of a top transaction card in a stack may be seen.
Any number of transaction cards may be included in a multi-pack of transaction cards. That is, while multi-packs which include three transaction cards or four transaction cards have been described, multi-packs are not limited to including three transaction cards or four transaction cards. Multi-packs may include fewer than three transaction cards or more than four transaction cards.
While a carrier card arrangement has been described as including more than one of the same transaction card, it should be appreciated that a carrier assembly may include different transaction cards. That is, a multi-pack of transaction cards is not limited to including one version of a transaction card. In one embodiment, the transaction cards included in a multi-pack may be associated with different values or denominations. In another embodiment, the transactions cards included in a multi-pack may be of different designs, e.g., color schemes.
As described above, a carrier card arrangement may have an overall activation code printed or otherwise provided thereon which may be used to activate substantially all transaction cards mounted on or within the carrier card arrangement. However, the overall activation code is not limited to being printed on or otherwise provided with a carrier card arrangement. For example, the overall activation code may be an activation code associated with a parent transaction card. That is, an activation code associated with a parent transaction card may be configured to activate the parent transaction card as well as associated child transaction cards. Hence, by reading the activation code from a parent transaction card mounted on a carrier card, substantially all the transaction cards mounted on the carrier card may then be activated.
The operations associated with the various methods of the present invention may vary widely. By way of example, steps may be added, removed, altered, combined, and reordered without departing from the spirit or the scope of the present invention.
The many features and advantages of the present invention are apparent from the written description. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.
The present invention is a continuation-in-part application to U.S. patent application Ser. No. 12/041,536, filed Mar. 3, 2008, and entitled “Multi-Pack Gift Card and Activation Thereof”, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
846064 | Souder | Mar 1907 | A |
3346294 | Sartz | Oct 1967 | A |
4319684 | Backman et al. | Mar 1982 | A |
4828105 | Silengo et al. | May 1989 | A |
5036645 | Schwarz | Aug 1991 | A |
5135157 | Cruz | Aug 1992 | A |
5139454 | Earnest | Aug 1992 | A |
5143279 | Gaines | Sep 1992 | A |
5219184 | Wolf | Jun 1993 | A |
5263586 | Keable | Nov 1993 | A |
D344757 | Kruyt | Mar 1994 | S |
5467917 | Potter | Nov 1995 | A |
5516033 | Bernetich | May 1996 | A |
5573117 | Adams | Nov 1996 | A |
5575384 | Saye | Nov 1996 | A |
5626551 | Kearns et al. | May 1997 | A |
5641115 | Brewster | Jun 1997 | A |
5645214 | Taganas | Jul 1997 | A |
5650209 | Ramsburg et al. | Jul 1997 | A |
5687992 | Finkelshteyn | Nov 1997 | A |
5755375 | Rogers | May 1998 | A |
5760381 | Stich et al. | Jun 1998 | A |
5791474 | Hansen | Aug 1998 | A |
D400919 | Pickel | Nov 1998 | S |
5842629 | Sprague et al. | Dec 1998 | A |
5845425 | Leake et al. | Dec 1998 | A |
5862979 | Hill et al. | Jan 1999 | A |
5906063 | Magee, Sr. | May 1999 | A |
5918909 | Fiala et al. | Jul 1999 | A |
5941573 | Yordinsky | Aug 1999 | A |
5946834 | Bradley | Sep 1999 | A |
5947283 | Marshall | Sep 1999 | A |
5963915 | Kirsch | Oct 1999 | A |
5963916 | Kaplan | Oct 1999 | A |
5981040 | Rich et al. | Nov 1999 | A |
5984091 | Orr et al. | Nov 1999 | A |
6003254 | Lorber | Dec 1999 | A |
6050415 | Lind et al. | Apr 2000 | A |
6053321 | Kayser | Apr 2000 | A |
6070719 | Pollock | Jun 2000 | A |
6092841 | Best et al. | Jul 2000 | A |
6199912 | Finkelshteyn | Mar 2001 | B1 |
6224108 | Klure | May 2001 | B1 |
6233682 | Fritsch | May 2001 | B1 |
6244444 | Jacobus et al. | Jun 2001 | B1 |
D447055 | Several et al. | Aug 2001 | S |
6270012 | Dawson | Aug 2001 | B1 |
6299530 | Hansted et al. | Oct 2001 | B1 |
6349829 | Matheis et al. | Feb 2002 | B1 |
D457555 | Stephens-D'Angelo et al. | May 2002 | S |
6385596 | Ansell et al. | May 2002 | B1 |
6418648 | Hollingsworth et al. | Jul 2002 | B1 |
6457638 | Schmidt | Oct 2002 | B1 |
6491213 | Purcell | Dec 2002 | B2 |
6619480 | Smith | Sep 2003 | B2 |
6659271 | Parsons | Dec 2003 | B2 |
6698116 | Waldron | Mar 2004 | B2 |
6731312 | Robbin | May 2004 | B2 |
6957737 | Frederickson et al. | Oct 2005 | B1 |
D512456 | Diaz et al. | Dec 2005 | S |
7055740 | Schultz et al. | Jun 2006 | B1 |
D541647 | Ashby et al. | May 2007 | S |
7243839 | Beck et al. | Jul 2007 | B2 |
D548279 | Gulakos | Aug 2007 | S |
7277870 | Mourad et al. | Oct 2007 | B2 |
7278584 | Gandel et al. | Oct 2007 | B1 |
7322519 | Blank et al. | Jan 2008 | B2 |
7367504 | Lewis et al. | May 2008 | B2 |
7374095 | Blank et al. | May 2008 | B2 |
7409788 | Lauer et al. | Aug 2008 | B2 |
7490720 | Cole et al. | Feb 2009 | B2 |
7500604 | Holme | Mar 2009 | B2 |
7546288 | Springer et al. | Jun 2009 | B2 |
7584887 | Sanchez et al. | Sep 2009 | B1 |
7607574 | Kingsborough et al. | Oct 2009 | B2 |
7712741 | Lambert | May 2010 | B2 |
7740170 | Singh et al. | Jun 2010 | B2 |
7822640 | Arthur et al. | Oct 2010 | B2 |
7837125 | Biskupski et al. | Nov 2010 | B2 |
7896252 | Narlinger et al. | Mar 2011 | B2 |
8256682 | Chakiris et al. | Sep 2012 | B2 |
20010034703 | Picciallo et al. | Oct 2001 | A1 |
20010040115 | Wani et al. | Nov 2001 | A1 |
20010045738 | Klure | Nov 2001 | A1 |
20020002468 | Geisler et al. | Jan 2002 | A1 |
20020028321 | Feilen et al. | Mar 2002 | A1 |
20020080714 | Pierson et al. | Jun 2002 | A1 |
20020088855 | Hodes | Jul 2002 | A1 |
20020147683 | Capobianco et al. | Oct 2002 | A1 |
20020157974 | Krahn | Oct 2002 | A1 |
20020195816 | Anise | Dec 2002 | A1 |
20030004889 | Fiala et al. | Jan 2003 | A1 |
20030018586 | Krahn | Jan 2003 | A1 |
20030066777 | Malone | Apr 2003 | A1 |
20030150142 | Street | Aug 2003 | A1 |
20030156686 | Pines | Aug 2003 | A1 |
20030230501 | Smolev | Dec 2003 | A1 |
20040064374 | Cho | Apr 2004 | A1 |
20040140361 | Paul et al. | Jul 2004 | A1 |
20040140616 | Davis | Jul 2004 | A1 |
20040254836 | Emoke Barabas et al. | Dec 2004 | A1 |
20040267622 | Taylor et al. | Dec 2004 | A1 |
20040268386 | Logan et al. | Dec 2004 | A1 |
20050017502 | Chariker | Jan 2005 | A1 |
20050100312 | Commons et al. | May 2005 | A1 |
20050167301 | Oram | Aug 2005 | A1 |
20050167910 | Candler | Aug 2005 | A1 |
20050171795 | Kearby et al. | Aug 2005 | A1 |
20050182675 | Huettner | Aug 2005 | A1 |
20050279825 | Ashby et al. | Dec 2005 | A1 |
20060032764 | Swenson | Feb 2006 | A1 |
20060042986 | Simkowski | Mar 2006 | A1 |
20060065748 | Halbur et al. | Mar 2006 | A1 |
20060086630 | Cheong et al. | Apr 2006 | A1 |
20060118618 | Schultz et al. | Jun 2006 | A1 |
20060185201 | Fachon et al. | Aug 2006 | A1 |
20060212401 | Ameerally et al. | Sep 2006 | A1 |
20060224516 | Lemon et al. | Oct 2006 | A1 |
20060235864 | Hotelling et al. | Oct 2006 | A1 |
20060243609 | Cole et al. | Nov 2006 | A1 |
20060259189 | Perlow et al. | Nov 2006 | A1 |
20060261154 | Arthur et al. | Nov 2006 | A1 |
20070017973 | Blank et al. | Jan 2007 | A1 |
20070038577 | Werner et al. | Feb 2007 | A1 |
20070063052 | Chakiris et al. | Mar 2007 | A1 |
20070090184 | Lockwood et al. | Apr 2007 | A1 |
20070154167 | Ando et al. | Jul 2007 | A1 |
20070174200 | Sung-Min et al. | Jul 2007 | A1 |
20070187492 | Graves et al. | Aug 2007 | A1 |
20070198418 | Macdonald et al. | Aug 2007 | A1 |
20070208664 | Ortega | Sep 2007 | A1 |
20070224969 | Rao | Sep 2007 | A1 |
20070267502 | Zellner et al. | Nov 2007 | A1 |
20070278280 | Wert et al. | Dec 2007 | A1 |
20070289890 | Appelbaum | Dec 2007 | A1 |
20080052371 | Partovi et al. | Feb 2008 | A1 |
20080116088 | Roberts | May 2008 | A1 |
20080116089 | Roberts | May 2008 | A1 |
20080120609 | Gates et al. | May 2008 | A1 |
20080154722 | Galinos | Jun 2008 | A1 |
20080159715 | Fuasaro et al. | Jul 2008 | A1 |
20080188209 | Dorogusker et al. | Aug 2008 | A1 |
20080190267 | Rechstein et al. | Aug 2008 | A1 |
20080320139 | Fukuda et al. | Dec 2008 | A1 |
20090063292 | Cole et al. | Mar 2009 | A1 |
20090104539 | Watanabe et al. | Apr 2009 | A1 |
20090218392 | Biskupski et al. | Sep 2009 | A1 |
20090283594 | Walton et al. | Nov 2009 | A1 |
20100219099 | Schmitt et al. | Sep 2010 | A1 |
20100253063 | Skogster | Oct 2010 | A1 |
20110137793 | Liggett | Jun 2011 | A1 |
20120025516 | Miller et al. | Feb 2012 | A1 |
20120234909 | Tang | Sep 2012 | A1 |
20120259718 | Miller et al. | Oct 2012 | A1 |
Number | Date | Country |
---|---|---|
0725376 | Aug 1996 | EP |
0927945 | Jul 1999 | EP |
1111562 | Jun 2001 | EP |
2827981 | Jan 2003 | FR |
WO9924942 | May 1999 | WO |
WO0028461 | May 2000 | WO |
WO0043852 | Jul 2000 | WO |
WO0062265 | Oct 2000 | WO |
WO0141023 | Jun 2001 | WO |
WO0144908 | Jun 2001 | WO |
WO0146786 | Jun 2001 | WO |
WO0150305 | Jul 2001 | WO |
WO0208869 | Jan 2002 | WO |
WO 03007233 | Jan 2003 | WO |
2004038567 | May 2004 | WO |
2004044770 | May 2004 | WO |
Entry |
---|
“Identification Cards—Recording Technique—Part 7: Magnetic Strip—High Coercivity, High Density”, ISO Standard, ISO/IEC 7811-7:2004 downloaded Dec. 26, 2007, 2 pgs. |
“American National Standard Specifications for Credit Cards”, American National Standards Institute, Inc. (ANSI), x4.13/1971, 1971, 18 pgs. |
“American National Standard Magnetic-Stripe Encoding for Credit cards”, American National Standards Institute, Inc. (ANSI), x4.16/1976, 1976, 12 pgs. |
Offenberg, J. “Markets—Gift Cards”, Journal of Economic Perspectives, vol., 21, No. 2, Spring 2007, pp. 227-238. |
U.S. Appl. No. 11/965,674, entitled “Methods and Systems for Encoding a Magnetic Stripe”, filed Dec. 27, 2007. |
U.S. Appl. No. 12/041,536, entitled “Multi-Pack Gift Card and Activation Thereof”, filed Mar. 3, 2008. |
U.S. Appl. No. 12/197,975, entitled “Carrier Card Arrangement with Removable Envelope”, filed Aug. 25, 2008. |
“Identification Cards-Recording Technique”, International Standard ISO/IEC, vol. 7811-2, No. Third Edition, Feb. 1, 2001, pp. 1-21. |
Pottery Barn, Gift Cards, Web Page, downloaded Jun. 27, 2008, 1 pg. |
“list.” Dictionary of Publishing and Printing. London: A&C Black, 2006, www.credoreference.com/entry/acbpublishing/list, p. 1. |
“listing.” Collins English Dictionary. London: Collins, 2000, www.credoreference.com/entry/hcengdict/listing, p. 1. |
“bin.” Collins English Dictonary, London: Collins, 2000, www.credoreference.com/entry/hcengdict/bin, p. 1. |
“rack 1”,Collins English Dictonary, London, Collins 2000, www.credoreference.com/entry/hcengdict.rack—l , 1 pg. |
“price”, Chambers 21st Centruy Dictonary, London, Chambers Harrap, 2001, www.credoreference.com/entry/chambdict/price, 1 pg. |
“allow”, Webster's Third New International Dictionary, Merriam-Webster, downloaded Jul. 14, 2009, http://lionreference.chadwyck.com/searchFulltext.do?id=871261&idType=offset&divLevel=2&queryId../sessions/1247680262—19043&area=mwd&forward=refshelf&trail=refshelf, 2 pg. |
“value”, Webster's Third New International disconary, Merriam-Webster, Incorporated, downloaded Jul. 15, 2009, http://lionreference.chadwyck.com/searchFulltext.do?id=38664807&idTyple=offset&divLevel=2&queryID../session/1247683362—2487&area=mwd&forward=refshelf&trail=refshelf, p. 4. |
“media”, Chambers 21st Century Dictionary, London, Chambers Harrap, 2001, downloaded Jul. 15, 2009, www.credoreference.com/entry/chambdict/media.com, 1 pg. |
“associate”, Collins English Dictionary, London, Collins 2000, www.credoreference.com/entry/hcengdict/associate, 1 pg. |
“active”, Webster's Third New International Dictionary, Merriam-Webster, Inc., downloaded Jul. 16, 2009, http://lionreference.chadwyck.com/searchFulltextdo?id=313560&idType=offset&divLevel=2&queryID../session/1247778592—27918&area=mwd&forward=refshelf&trail=refshelf, 3 pg. |
“activate”, Webster's Third New International Dictionary, Merriam-Webster, Inc., downloaded Jul. 16, 2009, http://lionreference.chadwyck.com/searchFulltext.do?id=312239&idType=offset&divLevel=2&queryID../session/1247778879—29216&area=mwd&forward=refshelf&trail=refshelf, 2 pg. |
The Bank Credit Card Business, 2nd Edition, American Bankers Association, Washington D.C., 1996, pp. 1-13, 63-89. |
Smart Card Handbook, 2nd Edition, W. Rankl and W. Effing, John Wiley and Sons, West Sussex, England, 2000, 49 pgs. |
Number | Date | Country | |
---|---|---|---|
20090218392 A1 | Sep 2009 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12041536 | Mar 2008 | US |
Child | 12262097 | US |