This application is related to commonly owned U.S. patent application Ser. No. 11/380,888 filed Apr. 28, 2006 and entitled “Transaction Card Package Assembly Having Enhanced Security,” which is hereby incorporated by reference herein in its entirety.
Not applicable.
Not applicable.
The present invention generally relates to package assemblies for transaction cards such as gift cards, debit cards, credit cards, and the like.
The market for transaction cards such a merchant gift cards continues to grow. Such cards may be subject to fraud, for example by a thief removing a valid gift card from a card holder that is used to activate the card, and inserting a fraudulent gift card in the holder. This activity, sometimes referred to a swapping, results in activation of the valid card held by the thief and non-activation of the fraudulent card held by the unsuspecting consumer. As a result, an ongoing need exists for improved transaction card package assemblies, which is addressed by the present disclosure.
A transaction card package assembly comprising a transaction card held by a card holder and having a security code spanning the transaction card and the card holder such that upon removal of the transaction card from the card holder, the security code is broken and a portion of the security code remains on the transaction card and a portion of the security code remains on the card holder.
A transaction card package assembly system comprising a first package assembly comprising a first transaction card held by a first card holder and having a first security code spanning the first transaction card and the first card holder such that upon removal of the first transaction card from the first card holder, the first security code is broken and a portion of the first security code is present on the first transaction card and a portion of the first security code is present on the first card holder, and a second package assembly comprising a second transaction card held by a second card holder and having a second security code spanning the second transaction card and the second card holder such that upon removal of the second transaction card from the second card holder, the second security code is broken and a portion of the second security code is present on the second transaction card and a portion of the second security code is present on the second card holder, wherein upon placement of the first transaction card in the second card holder, or vice-versa, the security codes do not match, thereby providing an indication of possible tampering or fraudulent activity.
As used herein, transaction card refers to a card that may be used to transact business with a party willing to accept the card, for example as tender for a purchase. Examples of such cards include credit cards, debit cards, gift cards, telephone cards, loyalty cards, membership cards, ticket cards, entertainment cards, sports cards, prepaid cards, and the like. Typically, such cards are wallet-sized and made of plastic. In various embodiments, the transaction card may be a type of card such as a gift or prepaid card that requires activation at a point of sale. For example, a transaction card may be purchased and activated at a point of sale by a consumer and subsequently used by the consumer or another (e.g., the recipient of the card as a gift) to transact business.
Purchase of a transaction card may involve a card vendor, a redeeming merchant, and a card issuer. In various embodiments, the card vendor, redeeming merchant and card issuer may be the same, different, or related entities. The point of sale where the card is purchased and activated is referred to herein as the card vendor or simply vendor. An entity that will accept the card for business transactions, for example as tender for a purchase, is referred to as a redeeming merchant. An entity that provides the financial backing and/or payment processing accessed via the transaction card is referred to as the card issuer or simply issuer. Typically, the issuer is identified on the transaction card and associates a unique issuer account code with each transaction card. Card issuers include direct issuers of cards such as store-branded cards, and in some embodiments the card vendor may also be the card issuer and/or the redeeming merchant. Card issuers also include banks, financial institutions, and transaction processors such as VISA, Mastercard, American Express, etc., and cards issued by such institutions may be readily accepted by a number of redeeming merchants to conduct transactions such as purchases. In some instances, the redeeming merchant may be identified on the transaction card (for example, a retailer branded card such as Store X), and such cards may be sold at the same or different card vendor (e.g., card vendor is Store X or a different or unrelated Store Z). In such instances, the Store X branded transaction card may be issued by Store X, by Store Z, or by a third party such as bank or financial institution.
In an embodiment, a transaction card package assembly comprises a transaction card attached/coupled to or disposed/held within a card holder. The transaction card package assembly further comprises a security code spanning the transaction card and the card holder such that upon removal of the transaction card from the holder, the security code is broken and a portion of the security code is present on the transaction card and a portion of the security code is present on the card holder. The security code may be integral with and form a part of the transaction card and card holder, for example formed concurrently during molding and/or printing of the transaction card and/or the card holder. Alternatively, the security code may be external to the transaction card and card holder, for example printed and/or applied via a sticker or other external layer applied/adhered to the transaction card and card holder.
Upon removal of the transaction card from the card holder, the security code is broken and a portion of the security code remains on the transaction card and a portion of the security code remains on the card holder. The broken portions of the security code are configured such that they may not be readily removed from their respective substrate and applied to another substrate, and in particular without damaging or destroying the security code portion and/or the substrate. For example, where the security code is integral with the transaction card and card holder, e.g., printed and/or embossed in a manner that spans each, such printing and/or embossing may be difficult or nearly impossible to remove from the transaction card and/or card holder and place on a substitute transaction card and/or card holder, respectively. As another example, where the security code is printed on a sticker or other layer that spans the transaction card and the card holder, the sticker or other layer should be sufficiently adhered, affixed, or otherwise configured (for example, with serrations, such that the portions of the sticker or other layer remaining on the transaction card and/or card holder would be difficult or nearly impossible to remove intact and place on a substitute transaction card and/or card holder, respectively.
Given that each security code is unique, portions of security codes from different transaction cards and card holders will not match, and thus will be readily identifiable, for example by visible and/or tactile inspection, by a merchant or consumer as an indicator of possible tampering or fraudulent activity. For example, in the event that a first transaction card is removed from a first card holder (thereby breaking a first security code with portions thereof remaining on the first transaction card and first card holder) and a second transaction card is removed from a second card holder (thereby breaking a second security code with portions thereof remaining on the second transaction card and second card holder), the portions of the first and second security codes do not match when the first transaction card is placed in the second card holder or vice-versa.
The security code is unique to each transaction card package assembly, and the uniqueness of the security code provides a means to detect potentially fraudulent activity and/or to disable a package assembly subject to fraudulent activity. The security code may comprise a series of letters, numerals, characters, or combinations thereof. Such letters, numerals, characters, and combinations thereof may be readily found in any number of font sets. The security code may be randomly generated, and preferably contains a sufficient number of letters, numerals, characters, or combinations thereof to avoid an accidental duplication of the security code during manufacture of the transaction card package assembly. For example, the security code may include greater than 4, 6, 8, 10, 12, 14, etc. letters, numbers, characters, or combinations thereof, with a larger number being preferred. Alternatively or in addition to letters, numbers, and characters, the security code may comprise symbols, pictures, designs, graphics, or combinations thereof. In an embodiment, the security code is printed and/or embossed across a portion of the transaction card and card holder, for example across an interface such as a score or break line between the two.
In an embodiment, the security code is positioned such that a longitudinal center axis of the security code is in registration with the interface between the transaction card and the card holder, wherein upon breaking of the security code, a first longitudinal portion or half of the security code remains with the transaction card and a second longitudinal portion or half of the security code remains with the card holder. The interface between the transaction card and the card holder may be configured such that the transaction card disengages/releases from the card holder along the interface. In some embodiments, a retaining means may define the interface between the security code and the card holder. Non-limiting examples of retaining means include an adhesive, for example a contact adhesive such as rubberized glue or cement; hook and loop fastener; clips; rivets; snap and break connections; perforations; cut-outs, inserts, and/or pockets; or combinations thereof.
In an embodiment, the interface between the transaction card and the card holder may be a fault, break, score, or perforation line in a snap and break connection. For example, the transaction card and card holder may be molded from plastic with a score line defining the interface, whereby the transaction card may be removed from the card holder by folding the card along the score line wherein the plastic card snaps and breaks free from the plastic holder. In an alternative embodiment, the interface comprises a perforated line in a fold and tear connection. For example, the transaction card and the card holder may be printed on a sheet of rigid paper such as cardboard with a perforated line defining the interface, whereby the transaction card may be removed from the card holder by folding the card along the perforated line and tearing the card from the holder.
In certain embodiments, the security code may also serve a secondary or dual purpose, such as encoding information useful for purchase and/or activation of the transaction card. For example, the dual purpose security code may comprise a unique bar code that may be scanned at a point of sale terminal to purchase and/or activate the transaction card. An example of such a unique bar code is an EAN/UCC-128 bar code, containing both a vendor product identification portion and an issuer account portion. The EAN/UCC-128 bar code may be used to activate the card via a one-step process.
In a one-step activation sequence, the one step comprises simultaneously entering the combination vendor product identification and issuer account code at a point of sale terminal. The one-step process only requires a single entry by a clerk operating the point of sale terminal to activate the transaction card. For example, the one step may be performed at the point of sale terminal by scanning a bar code, for example an EAN/UCC-128 bar code, containing both a vendor product identification portion and an issuer account portion. The vendor product identification portion may be used to perform a look-up to determine product identity and price. The issuer account portion may be used to activate the particular account associated with the transaction card such that the card may be used to transact business with the issuer of the card. Upon being entered at the point of sale terminal, the issuer account code may be conveyed (for example, via a computer network) to the issuer or other third party processor responsible for looking up the account code (for example, via a database reconciliation) and activating same.
By breaking the dual purpose security code, the bar code is likewise broken, and thus is disabled and can not be used to purchase and/or activate the transaction card unless both potions are present and match. An attempt to fraudulently swap transaction cards in a holder fails because the portions of the unique bar code do not match, and thus may not be scanned. Furthermore, a mismatched security code provides a visual and/or tactile indication of possible tampering or fraudulent activity.
A first embodiment of a transaction card package assembly 20 is shown in the front view of
The retaining means 15 may define an interface 17, for example a score or break line in a snap and break connection (as shown), between the transaction card 10 and the card holder 22. As shown in
As shown in
Alternative types of security codes may provide mismatches that are more readily identifiable than with a bar code. Examples of alternative security codes include but are not limited to second embodiment of a transaction card package assembly 20 having an alpha numeric security code 46 (provided that each such alpha numeric code is unique) as shown in the back view of
A fourth embodiment of a transaction card package assembly 20 is shown in the front view of
A fifth embodiment of a transaction card package assembly 20 is shown in the front view of
Preferably, the retaining means 17 is a snap and break connection between a plastic transaction card 10 and panel 22 or a perforated connection between paper or cardboard transaction card 10 and panel 22. The length L1 of panel 22 may be greater than, less than, or preferably about equal to (as shown) the length L1 of the transaction card 10. Likewise, the width W1 of panel 22 may be greater than, equal to, or preferably less than (as shown) the width W2 of the transaction card 10. In an embodiment, W1 is less than about ¾ of W2, alternatively W1 is less than about ½ of W2, alternatively W1 is about ⅓ of W2. In an embodiment, the length L1 of panel 22 and transaction card 10 is about 3⅜ inches, the width W1 of the panel 22 is about ¾ inch, and the width W2 of the transaction card 10 is about 2⅛ inches.
A sixth embodiment of a transaction card package assembly 20 is shown in the front view of
The rack hanger 50 further comprises an opening 24 and window 26. Opening 24 may be a “sombrero” shaped aperture or cut-out suitable for hanging the package assembly 20 from a rod in a display rack or shelf in a retail store. The window 26 may be an aperture or cut-out, or alternatively may be a transparent portion such as a cut-out covered by a clear film. In the back view shown in
The length L2 of rack hanger 50 may be less than, equal to, or preferably greater than (as shown) the length L1 of the transaction card 10 and panel 22. Likewise, the width W3 of rack hanger 50 may be less than, equal to, or preferably greater than (as shown) the combined width W1+W2 of the transaction card 10 and panel 22. In an embodiment, the length L1 of panel 22 and transaction card 10 is about 3⅜ inches, the width W1 of the panel 22 is about ¾ inch, the width W2 of the transaction card 10 is about 2⅛ inches, the length L2 of rack hanger 50 is about 4 inches and the width W3 of rack hanger 50 is about 5¼ inches.
In an alternative embodiment of
The transaction card 10 may be folded and/or pulled forward away from the rack hanger 50, thereby snapping and breaking the interface 17 to remove the card from the package assembly 20. Alternatively, the transaction card 10 may be folded and/or pulled forward away from the rack hanger 50, thereby tearing the perforated interface 17 to remove the card from the package assembly 20. Upon removal of the card, the upper half of the snap and break or perforated connection, i.e., panel 22, remains affixed to the rack hanger 50. After activation of the transaction card 10 and removal of the card from the package assembly 20, the remainder of the package assembly may be discarded.
In alternative embodiments of
A seventh embodiment of a transaction card package assembly 20 is shown in the front view of
The use of an activation code on magnetic stripe 55 may help to prevent a fraudulent activity known as skimming, wherein the issuer account code is read from the magnetic stripe 32 on the card (for example with a handheld magnetic stripe reader) and a duplicate, fraudulent card is produced having the same issuer account code. Upon activation of the card 10 by an unsuspecting customer, the fraudulent duplicate card is likewise activated and can be used by a thief. In addition to providing a useless activation code upon being skimmed (rather than the actual issuer account code), the second panel 53 further provides a physical barrier that prevents swiping of the bar code 32 on the card 10, and thereby provides an additional protection again skimming. For example, the width W4 of the panel 53 may be selected such that the bar code 32 on card 10 is positioned above the normal slot depth of a magnetic card reader, and thus cannot be easily swiped by such readers in an effort to skim the card. In an embodiment, the width W4 is greater than about ½ inch, alternatively greater than about ¾ inch, alternatively greater than about 1 inch.
An eighth embodiment of a transaction card package assembly 20 is shown in the front view of
The rack hanger 50 further comprises an opening 24 and window 26. Opening 24 may be a “sombrero” shaped aperture or cut-out suitable for hanging the package assembly 20 from a rod in a display rack or shelf in a retail store. The window 26 may be an aperture or cut-out, or alternatively may be a transparent portion such as a cut-out covered by a clear film. In the back view shown in
In an alternative embodiment of
The transaction card 10 may be folded and/or pulled forward away from the rack hanger 50, thereby snapping and breaking the interface 17 to remove the card from the package assembly 20. Alternatively, the transaction card 10 may be folded and/or pulled forward away from the rack hanger 50, thereby tearing the perforated interface 17 to remove the card from the package assembly 20. Upon removal of the card, the upper half of the snap and break or perforated connection, i.e., panel 22, remains affixed to the rack hanger 50. Likewise, lower panel 53 may be removed from the card before or after removal of the card from panel 22, for example via snapping and breaking along the interface 57. After activation of the transaction card 10 and removal of the card from the package assembly 20, the remainder of the package assembly may be discarded.
Package assembly embodiments as described herein may be manufactured according to various methods known in the art. For example, transaction cards and card holders can be manufactured and printed and subsequently placed in a printed rack hanger, or alternatively the transaction card and card holder can be made concurrently, for example via coextrusion of a plastic sheet with subsequent printing and placed in a printed rack hanger. Where made of a plastic or polymer, the type of material may be selected to provide appropriate functional characteristics such as printability, gloss, the ability to snap and break along a score, etc. In an embodiment, an existing transaction card 10 is retrofitted connecting the card 10 with panel 22 using a retaining means 15, and optionally subsequently attaching the card 10 and panel 22 to a rack hanger via attachment means 52. In some embodiment, security codes may be applied to prefabricated package assemblies via stickers spanning the transaction card and the card holder. Alternative methods of making the various embodiments disclosed herein will be apparent to those skilled in the art.
While preferred embodiments of the invention have been shown and described, modifications thereof can be made by one skilled in the art without departing from the spirit and teachings of the invention. The embodiments described herein are exemplary only, and are not intended to be limiting. Many variations and modifications of the invention disclosed herein are possible and are within the scope of the invention. Where numerical ranges or limitations are expressly stated, such express ranges or limitations should be understood to include iterative ranges or limitations of like magnitude falling within the expressly stated ranges or limitations (e.g., from about 1 to about 10 includes, 2, 3, 4, etc.; greater than 0.10 includes 0.11, 0.12, 0.13, etc.). Use of the term “optionally” with respect to any element of a claim is intended to mean that the subject element is required, or alternatively, is not required. Both alternatives are intended to be within the scope of the claim. Use of broader terms such as comprises, includes, having, etc. should be understood to provide support for narrower terms such as consisting of, consisting essentially of, comprised substantially of, etc.
Accordingly, the scope of protection is not limited by the description set out above but is only limited by the claims which follow, that scope including all equivalents of the subject matter of the claims. Each and every claim is incorporated into the specification as an embodiment of the present invention. Thus, the claims are a further description and are an addition to the preferred embodiments of the present invention. The discussion of a reference in the Description of Related Art is not an admission that it is prior art to the present invention, especially any reference that may have a publication date after the priority date of this application. The disclosures of all patents, patent applications, and publications cited herein are hereby incorporated by reference, to the extent that they provide exemplary, procedural or other details supplementary to those set forth herein.
Number | Name | Date | Kind |
---|---|---|---|
4722376 | Rhyner | Feb 1988 | A |
4887763 | Sano | Dec 1989 | A |
4937963 | Barnes | Jul 1990 | A |
5281799 | McIntire et al. | Jan 1994 | A |
5390794 | Vulpitta | Feb 1995 | A |
5399021 | Litt | Mar 1995 | A |
5609253 | Goade, Sr. | Mar 1997 | A |
D385488 | Smith et al. | Oct 1997 | S |
5720158 | Goade, Sr. | Feb 1998 | A |
5735550 | Hinkle | Apr 1998 | A |
5740915 | Williams | Apr 1998 | A |
D394387 | Williams | May 1998 | S |
5760381 | Stich et al. | Jun 1998 | A |
5777305 | Smith et al. | Jul 1998 | A |
5791474 | Hansen | Aug 1998 | A |
5839763 | McCannel | Nov 1998 | A |
5842629 | Sprague et al. | Dec 1998 | A |
D411765 | Holihan | Jul 1999 | S |
5918909 | Fiala et al. | Jul 1999 | A |
5921584 | Goade, Sr. | Jul 1999 | A |
5949058 | Kimura | Sep 1999 | A |
5958174 | Ramsberg et al. | Sep 1999 | A |
5969324 | Reber et al. | Oct 1999 | A |
5975302 | Young | Nov 1999 | A |
5997042 | Blank | Dec 1999 | A |
6053321 | Kayser | Apr 2000 | A |
6076296 | Schaeffer | Jun 2000 | A |
6089611 | Blank | Jul 2000 | A |
6109439 | Goade, Sr. | Aug 2000 | A |
6161870 | Blank | Dec 2000 | A |
6173901 | McCannel | Jan 2001 | B1 |
6199757 | Kubert | Mar 2001 | B1 |
6224108 | Klure | May 2001 | B1 |
6270012 | Dawson | Aug 2001 | B1 |
6305717 | Chess | Oct 2001 | B1 |
6315206 | Hansen et al. | Nov 2001 | B1 |
6328341 | Klure | Dec 2001 | B2 |
6358607 | Grotzner et al. | Mar 2002 | B1 |
6418648 | Hollingsworth et al. | Jul 2002 | B1 |
6439613 | Klure | Aug 2002 | B2 |
6454165 | Dawson | Sep 2002 | B1 |
6457649 | Hileman | Oct 2002 | B1 |
6471127 | Pentz et al. | Oct 2002 | B2 |
6543809 | Kistner et al. | Apr 2003 | B1 |
6588658 | Blank | Jul 2003 | B1 |
6619480 | Smith | Sep 2003 | B2 |
6640974 | Malone | Nov 2003 | B2 |
6679970 | Hwang | Jan 2004 | B2 |
6698116 | Waldron | Mar 2004 | B2 |
6708820 | Hansen et al. | Mar 2004 | B2 |
6715795 | Klure | Apr 2004 | B2 |
6729656 | Kubert et al. | May 2004 | B2 |
D493829 | Foster | Aug 2004 | S |
6832720 | Dawson | Dec 2004 | B2 |
6918537 | Graves et al. | Jul 2005 | B2 |
6929413 | Schofield | Aug 2005 | B2 |
D509654 | Miller | Sep 2005 | S |
6957737 | Frederickson et al. | Oct 2005 | B1 |
7083086 | Whitaker | Aug 2006 | B2 |
7188762 | Goade et al. | Mar 2007 | B2 |
7370805 | Smith et al. | May 2008 | B2 |
7413120 | Lewis et al. | Aug 2008 | B2 |
20020100797 | Hollingsworth et al. | Aug 2002 | A1 |
20020185543 | Pentz et al. | Dec 2002 | A1 |
20030004889 | Fiala et al. | Jan 2003 | A1 |
20030018586 | Krahn | Jan 2003 | A1 |
20030057274 | Dawson | Mar 2003 | A1 |
20030066777 | Malone | Apr 2003 | A1 |
20030106935 | Burchette, Jr. | Jun 2003 | A1 |
20030132132 | Small | Jul 2003 | A1 |
20030150762 | Biller | Aug 2003 | A1 |
20040182940 | Biller | Sep 2004 | A1 |
20050061889 | McGee et al. | Mar 2005 | A1 |
20050080730 | Sorrentino | Apr 2005 | A1 |
20050140135 | Miller et al. | Jun 2005 | A1 |
20050247798 | Graves et al. | Nov 2005 | A1 |
20060006225 | Goade, Sr. et al. | Jan 2006 | A1 |
20070090184 | Lockwood et al. | Apr 2007 | A1 |
20070102532 | Lubow | May 2007 | A1 |
Number | Date | Country | |
---|---|---|---|
20070251995 A1 | Nov 2007 | US |