Source: http://www.google.com/patents/US20050133590?dq=5,371,548
Timestamp: 2014-03-15 06:27:45
Document Index: 280328204

Matched Legal Cases: ['arty 405', 'arty 405', 'arty 405', 'arty 405', 'arty 405', 'arty 405', 'arty 405', 'arty 405']

Patent US20050133590 - System and method for redeeming rewards and incentives - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsTransaction card comprising a substrate having a front face and a back face, a first magnetic stripe for storing data associated with a credit account, the first magnetic stripe being located along an edge of the back face, a second magnetic stripe for storing data associated with a rewards account,...http://www.google.com/patents/US20050133590?utm_source=gb-gplus-sharePatent US20050133590 - System and method for redeeming rewards and incentivesAdvanced Patent SearchPublication numberUS20050133590 A1Publication typeApplicationApplication numberUS 10/740,707Publication dateJun 23, 2005Filing dateDec 18, 2003Priority dateDec 18, 2003Also published asUS7090138, US7370811, US7597255, US20060027647, US20060249575, WO2005062239A1Publication number10740707, 740707, US 2005/0133590 A1, US 2005/133590 A1, US 20050133590 A1, US 20050133590A1, US 2005133590 A1, US 2005133590A1, US-A1-20050133590, US-A1-2005133590, US2005/0133590A1, US2005/133590A1, US20050133590 A1, US20050133590A1, US2005133590 A1, US2005133590A1InventorsJessica Rettenmyer, Robert Greenberg, Chitra JainOriginal AssigneeRettenmyer Jessica A., Greenberg Robert J., Chitra JainExport CitationBiBTeX, EndNote, RefManReferenced by (13), Classifications (26), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetSystem and method for redeeming rewards and incentivesUS 20050133590 A1Abstract Transaction card comprising a substrate having a front face and a back face, a first magnetic stripe for storing data associated with a credit account, the first magnetic stripe being located along an edge of the back face, a second magnetic stripe for storing data associated with a rewards account, the second magnetic stripe being located along another edge of the back face, and account information located on the front face, the account information being associated with the credit account and the rewards account. Images(8) Claims(26)
FIELD The present application relates to a system and method for redeeming rewards and incentives and, more particularly, to a system and method for redeeming rewards and incentives using a transaction card having at least two magnetic stripes. BACKGROUND Numerous financial institutions, such as credit card companies and banks, and other entities, such as airline carriers, hotels and retailers, offer membership reward programs. These programs often reward participants with fictitious reward units, such as points or the like, when purchasing merchandise or services from merchants using a qualified account, such as a debit or credit account. A participant may use a transaction card associated with the qualified account to conduct the respective transaction. Reward units typically accrue at a rate of one unit for every dollar spent using the credit or debit account and the accrued units operate as currency. Some entities restrict purchasing to particular merchants to earn reward units, whereas other financial institutions have no such restrictions. The maximum reward units a participant can earn annually are usually unlimited. Additionally, reward units usually do not accumulate on cash advances, convenience checks, balance transfers, fees or adjustments. When merchandise purchased with the respective account is returned, the account credit will result in a reduction of reward units. Participants usually seek to accumulate enough reward units to purchase merchandise or services. For instance, a participant may seek to accumulate enough reward units to purchase a particular product from an associated merchant or purchase an airline ticket from another associated merchant. Depending on the program, only certain merchants are considered qualified merchants with whom reward units can be redeemed towards a purchase. Membership reward programs also often offer participants other rewards, incentives or the like instead of or in addition to the ability to accumulate reward units. For example, some membership reward programs return to a participant a predetermined percentage of a transaction amount or of an amount spent during a predetermined period (referred to as �cash back�) either as a credit to an account or by check, offer participants discounts on select merchandise or services, and complimentary merchandise or services. As described above, a transaction card having a magnetic stripe associated with a debit or credit account can be used by a participant to conduct a transaction and hence earn reward units and/or other rewards, incentives or the like, assuming the participant is entitled to such rewards, incentives or the like, for instance, if the participant is enrolled in a membership reward program. The accumulated rewards, incentives or the like cannot be redeemed with the transaction card, as the transaction card only has one magnetic stripe associated with a credit or debit account. Instead, other known methods for redemption are utilized by participants. Transaction cards having more than one magnetic stripe are known in the art. However, the magnetic stripes are operable, for example, for access to separate debit accounts having funds deposited therein and accounts having credit lines associated therewith and are operable, for example, to separate transactions at the point-of-sale, such as business expenses and personal expenses. A need, however, exists for a system and method that enables a cardholder to accumulate rewards, incentives or the like and to redeem at least a portion of those rewards, incentives or the like using a particular dedicated magnetic stripe located on a transaction card having at least one other magnetic stripe. SUMMARY An aspect of the present application provides for a transaction card, comprising a substrate having a front face and a back face, a first magnetic stripe for storing data associated with a credit account, the first magnetic stripe being located along an edge of the back face, a second magnetic stripe for storing data associated with a rewards account, the second magnetic stripe being located along another edge of the back face, and account information located on the front face, the account information being associated with the credit account and the rewards account. Another aspect of the present application provides for a transaction card, comprising a substrate having a front face and a back face, a first magnetic stripe for storing data associated with a credit account, the first magnetic stripe being located along an edge of the back face, and a second magnetic stripe for storing data associated with a rewards account, the second magnetic stripe being located along another edge of the back face, the second magnetic stripe including a plurality of data fields, data stored or no data being stored in at least one of the plurality of data fields identifying the second magnetic stripe as being associated with the rewards account, wherein account information is located on the front face, the account information being associated with the credit account and the rewards account, and the rewards account has a balance equal to a number of accumulated reward units, the reward units operable as currency with at least one of a plurality of merchants suing the second magnetic stripe. A further aspect of the present application provides for a transaction card, comprising a substrate having a front face and a back face, a first magnetic stripe for storing data associated with a credit account, the first magnetic stripe being located along an edge of the back face, a second magnetic stripe for storing data associated with a rewards account, the second magnetic stripe being located along another edge of the back face, first account information located on the front face, the first account information being associated with the credit account, and second account information located on the front face, the second account information being associated with the rewards account. A still further aspect of the present application provides for a method for processing a transaction initiated with a merchant using a transaction card having at least two magnetic stripes, the method comprising receiving data associated with the transaction, the data including a purchase amount, determining according to the received data whether a first magnetic stripe or a second magnetic stripe was read at the merchant, the second magnetic stripe being associated with a rewards account, converting the purchase amount to an amount of reward units, if it is determined that the second magnetic stripe was read at the merchant, and determining whether the rewards account has a balance of reward units at least equal to the amount of converted reward units.
DETAILED DESCRIPTION FIG. 1 depicts an exemplary reward accumulation and redemption system 100. Reward accumulation and redemption system 100 enables a participant in a reward program (hereinafter referred to as �cardholder 145�) to earn rewards, incentives or the like, for instance, by engaging in transactions with merchants using a transaction card associated with a qualified financial account, and later redeeming those accumulated rewards, incentives or the like using the same transaction card with those merchants or with other merchants. An exemplary transaction card of the present application, transaction card 150, includes at least two magnetic stripes, as illustrated in FIGS. 2, 3 and 4 and described herein. In an exemplary embodiment of the present application, cardholder 145 has the ability to earn a plurality of reward units, such as points, for example, for purchases with merchants 140 a . . . 140 n using qualified financial account 305, such as a credit or debit account, shown in FIGS. 3 and 4, as described herein. The present application is applicable, to any institution or company having a membership reward program associated therewith, including financial institutions, airlines, supermarkets, hotels, car rental companies, retail stores, Internet loyalty programs, loyalty providers, such as Carlson Companies, Inc. and Cendant Corporation, and Visa� and MasterCard� that offer rewards, incentives or the like. In an exemplary embodiment of the present application, the membership reward program is managed directly by the institution or company, for instance, financial institution 315, as seen in FIG. 3. Alternatively, the membership reward program is managed by a third party, for instance, third party 405 associated with financial institution 315, as depicted in FIG. 4. Financial institution 315 may or may not in a partnership with third party 405 and/or other party. For instance, in the event financial institution 315 has a partnership relationship with third party 405 and/or other party, the relationship may involve a co-branding. The membership reward program can also be operable as an independent reward program, as an accelerator reward program, as a coalition reward program or otherwise, or as a combination thereof. As would be appreciated by a person having ordinary skill in the art, when enrolled in an accelerator program, a participant accelerates the earning of reward units or the like in another reward program independent of the accelerator program, for example, when conducting transactions with an account linked to the accelerator program. A coalition reward program, such as Upromise (www.upromise.com), is operable for participants to earn rewards from a particular suite of merchants. Other reward programs can be associated with the coalition reward program. When a participant conducts a transaction with one of the merchants within the suite using one of these other reward programs, that participant earns additional rewards. For instance, a reward program associated with a coalition reward program is operable for participants to earn X % for every transaction regardless of the merchant and an additional Y % for transactions conducted with one of the merchants within the suite and an additional Z % at another one of the merchants within the suite. Accordingly, two or more membership reward programs can be linked together so that a participant earns reward units or the like in a single rewards account 310, 410 from various sources. Reward system 100 includes exemplary transaction system 105 and exemplary rewards tracking system 110. Transaction system 105 is linked to a plurality of merchants 140 a . . . 140 n via credit/debit network 135. Transaction system 105 includes processing unit 115 and memory unit 120 coupled to processing unit 115, processing unit 115 managing and recording data associated with transactions between cardholder 145 and merchants 140 a . . . 140 n. Memory unit 120 is operable for storing personal information pertaining to each participant, including cardholder 145, and account data pertaining to the respective participants, for example, account number(s) and transaction data. Memory unit 120 can include various types of memory storage devices, for example, one or more databases, relational or otherwise and, therefore, is not meant to be limited to any particular type of storage device. Rewards tracking system 110 is linked to transaction system 105 and includes processing unit 125 coupled to memory unit 130. Rewards tracking system 110 can either be associated with the reward program offered, for example, by financial institution 315, associated with a third party, such as third party 405, having reward managing responsibilities for reward accumulation and/or reward redemption, or responsibilities can be shared between the respective parties. Processing unit 125 is operable for managing reward accrual and redemption, and memory unit 130 is operable for storing data regarding reward accrual and reward redemption for each respective participant including cardholder 145. Memory unit 130 can include various types of memory storage devices, for example, one or more databases, relational or otherwise and, therefore, is not meant to be limited to any particular type of storage device. In an exemplary embodiment, memory unit 130 and memory unit 120 are relational databases so that data can be stored in both memory units 130, 120 for cardholder 145. Alternatively, either memory unit 130 or memory unit 120 is included in reward system 100 and can be included in rewards tracking system 110, transaction system 105, or elsewhere. Similarly, either processing unit 115 or processing unit 125 can be included in reward system 100 and can be included in rewards tracking system 110, transaction system 105, or elsewhere. The functionality provided by reward tracking system 110 and transaction system 105 can also be provided by a single system, as opposed to separate systems linked together, such as rewards tracking system 110 and transaction system 105. Transactions and prospective transactions between cardholder 145 and merchants 140 a . . . 140 n are processed by processing unit 115 via credit/debit network 135. For instance, credit/debit network 135 could be the MasterCard�/Visa� network or other proprietary networks, such as Plus, Novus (debit), Diner's Club� (credit) and American Express�, the operation and use of which are well known in the art and are, thus, not described herein. Transactions between cardholder 145 and merchants 140 a . . . 140 n can be initiated at a point-of-sale (�POS�) terminal, through an Internet link, through a mail link or through a telephone link. In an exemplary embodiment, cardholder 145 purchases with qualified financial account 305 merchandise and services from or through any of the plurality of merchants 140 a . . . 140 n and earns rewards, incentives or the like, such as reward units, on those purchases since financial account 305 is associated with the reward program. The accumulated rewards, incentives or the like are reflected in rewards account 310, 410. Cardholder 145, however, can only use those earned reward units with those merchants, referred to hereinafter as qualified merchants, amongst merchants 140 a . . . 140 n that have a preexisting business arrangement with the reward program associated with financial account 305. Cardholder 145 is not restricted as to which of the plurality of merchants 140 a . . . 140 n, qualified or non-qualified, they can make purchases from or through. Furthermore, depending on the reward program, cardholder 145 may be able to redeem reward units for gift certificates, cash or the like and, therefore, have the ability to make purchases from any merchant amongst the plurality of merchants 140 a . . . 140 n, assuming the respective merchant accepts such gift certificates, cash or the like. As will be appreciated by a person having ordinary skill in the art, the present application is not limited to redemption within credit/debit network 135. Alternatively, cardholder 145 can use those earned reward units or other rewards, incentives or the like, with any one of the merchants 140 a . . . 140 n regardless of whether the respective merchant has a preexisting business arrangement with the reward program associated with financial account 305. Hence, the respective merchant processes the transaction using, for instance, the earned reward units as currency without being aware that a form of payment was used other than a cash reserve or a credit line. The exemplary embodiments of the present application are described herein with reference to reward units as being points, and earning and redeeming the same. The present application, however, is not limited to points, as points are units merely symbolizing a form of currency for use towards transactions. Hence, other symbols operable as currency are equally applicable to the exemplary embodiments of the present application, for instance, miles, stars, dollars, cash, rebates or credits. Further, the exemplary embodiments of the present application are described herein with reference to participants such as cardholder 145. Participants are individuals that have enrolled, for instance, in the membership reward program and therefore are entitled to earn and redeem points. Even though the exemplary embodiments are described herein with reference to such participants having membership in a reward program, alternatively, membership in a particular program is not a prerequisite for earning and redeeming rewards, incentives or the like. The components of FIG. 1 may be implemented through hardware, software, and/or firmware. The components in reward system 100 are not limited to those illustrated. Exemplary transaction card 150 is depicted in more detail in FIG. 2. Transaction card 150 includes front face 205 and back face 210. Transaction card 150 is a conventional transaction card except transaction card 150 includes conventional magnetic stripe 215 and an additional magnetic stripe�reward magnetic stripe 220 on back face 210. Reward magnetic stripe 220 is located along the bottom, horizontal side edge of transaction card 150, as can be seen in FIG. 2. Alternatively, the location of conventional magnetic stripe 215 and reward magnetic stripe 220 can be reversed from what is illustrated in FIG. 2. As will be appreciated by a person having ordinary skill in the art, conventional magnetic stripe 215 and reward magnetic stripe 220 each include at least one track having a plurality of data fields. FIGS. 6 and 7 illustrate two tracks associated with each magnetic stripe. Specifically, FIG. 6 illustrates exemplary data fields associated with track 1 605 of conventional magnetic stripe 215 and reward magnetic stripe 220 and FIG. 7 illustrates exemplary data fields associated with track 2 705 of conventional magnetic stripe 215 and reward magnetic stripe 220, track 1 605 and track 2 705 having exemplary data encoded thereon for illustration purposes. Alternatively, conventional magnetic stripe 215 and/or reward magnetic stripe 220 can have one track or can have more than two tracks. As will also be appreciated by a person having ordinary skill in the art, a magnetic stripe often has multiple tracks encoded with the same or similar data because different devices, such as POS terminals, automated teller machines or the like, may read different tracks. One of the multiple tracks may also be left empty�not encoded with any data. The exemplary embodiments of the present application, however, are equally applicable to a magnetic stripe having one track. The data fields of track 1 605 are encoded with data indicating, for instance, account number 610, card holder's name 615, expiration date 620, service code 625 and PIN verification (optional) 630, as depicted in FIG. 6. Track 1 605 also includes a discretionary data field 635, an operation of which is described herein. The data fields of track 2 705 are encoded with data indicating, for instance, account number 710, expiration date 715, service code 720 and PIN verification (optional) 725, as illustrated in FIG. 7. Track 2 705 also includes a discretionary data field 730, an operation of which is described herein. The present application is not limited to the data fields shown in FIGS. 6 and 7. For instance, additional data fields can be included, the size of a respective data field can be different and the ordering of the data fields in a respective track can be different. Transaction card 150 also includes indicia 230 on front face 205, indicia 230 being, for example, an account number, an expiration date and the name of cardholder 145. Besides conventional magnetic stripe 215 and reward magnetic stripe 220, back face 210 includes signature box 225. Front face 205 and rear face 210 can include various other information in addition to or in place of indicia 230 and signature box 225. In an alternative embodiment of the present application, front face 205 includes another set of indicia such that indicia 230 corresponds to financial account 305 and the other set of indicia corresponds to rewards account 310,410, or vice versa. FIG. 3 illustrates exemplary accounts accessible when using conventional magnetic stripe 215 and reward magnetic stripe 220. For instance, conventional magnetic stripe 215 is operable for accessing financial account 305 managed by financial institution 315. As described herein, financial account 305 can be a credit account, a debit account such as a checking account, savings account, a money market account or the like, a college fund account, a stored value account, or the like. Reward magnetic stripe 220 is operable for accessing rewards account 310 also managed by financial institution 315. In an exemplary embodiment, rewards account 310 has a balance equal to a number of accumulated reward units, for example, points. Alternatively, reward magnetic stripe 220 can be operable for accessing rewards account 410 managed by third party 405, as shown in FIG. 4. Third party 405 is linked to financial institution 315. As a result, data regarding the membership reward program managed by third party 405 is accessible to financial institution 315 so that financial institution 315 can accept or decline attempted transactions by cardholder 145, as described herein or third party 405 can accept or decline attempted transactions and transmit data indicating such a determination to financial institution 315. FIG. 5 illustrates an exemplary flow chart for accumulating and redeeming rewards, incentives or the like according to the exemplary embodiments of the present application. As points are accumulated by cardholder 145, the respective points are thereafter deposited in rewards account 310 (and/or rewards account 410), in 505. That is, the balance of rewards account 310 is increased according to a value attributed to the accumulated points. Points can be earned based on purchases with or without using transaction card 150, promotions, bonuses, incentives, points savings such as interest on points, redemption behavior or the like. Transaction card 150 is presented by cardholder 145 to one of the plurality of merchants 140 a . . . 140 n, for instance, at a POS terminal. The POS terminal or other device, alone or in combination with one or more additional devices, reads data stored in the plurality of data fields of either conventional magnetic stripe 215 or reward magnetic stripe 220 depending on which magnetic stripe was read. Each time transaction card 150 is read at one of the plurality of merchants 140 a . . . 140 n, the respective one of the plurality of merchants 140 a . . . 14 on transmits transaction data to processing unit 115 and processing unit 115 in turn receives the respective transaction data which includes at least a portion of the data read from the plurality of data fields via credit/debit network 135, in 510. Based on an evaluation of the received transaction data, processing unit 115 determines whether reward magnetic stripe 220 or conventional magnetic stripe 215 was read at merchant 140 a . . . 140 n, in 515. In an exemplary embodiment, processing unit 115 determines whether reward magnetic stripe 220 or conventional magnetic stripe 215 was read at merchants 140 a . . . 140 n by examining data stored in at least one predetermined data field of the respective magnetic stripe, for example, discretionary data stored in discretionary data fields 635, 730 shown in FIGS. 6 and 7, respectively. For instance, the predetermined data field(s) of the reward magnetic stripe 220 includes data, whereas the corresponding data field of the conventional magnetic stripe 215 does not contain any data. Hence, processing unit 115 determines that reward magnetic stripe 220 was read by the presence of data in the at least one predetermined data field. Alternatively, the predetermined data field(s) of the conventional magnetic stripe 215 and the corresponding data field(s) of the reward magnetic stripe 220 contain different data. As a result, processing unit 115 determines whether reward magnetic stripe 220 or conventional magnetic stripe 215 was read at merchants 140 a . . . 140 n by examining the content of the respective data fields. In an exemplary embodiment, the same data is encoded in track 1 605 and track 2 705 of reward magnetic stripe 220 since different POS terminals or other devices may read different tracks of reward magnetic stripe 705. Some POS terminals or other devices may even read both tracks. Alternatively, track 1 605 and track 2 705 are not encoded with any data. As will be appreciated by a person having ordinary skill in the art, the present application is not limited to the above-described manners of determining which magnetic stripe was read at one of the plurality of merchants 140 a . . . 140 n. Other manners can be used instead of or in addition to the manners described herein that are within the scope of the present application. In an exemplary embodiment, data is stored in the predetermined data field(s) at the time one or more of the other data fields is coded with data, such as account data. If processing unit 115 determines that conventional magnetic stripe 215 was read at merchant 140 a . . . 140 n, then at least a portion of the transaction data indicating the account number is used by processing unit 115 to process the transaction initiated by cardholder 145 in a conventional manner for processing credit or debit transactions which are well known to a person having ordinary skill in the art, in 520. Further, in an exemplary embodiment, assuming the transaction is authorized, at least a portion of the received transaction data is transmitted to rewards tracking system 110 so that the respective amount of reward units (points) earned based on the amount of the transaction is deposited in rewards account 310, 410. If processing unit 115 determines, however, that reward magnetic stripe 220 was read at merchant 140 a . . . 140 n, then at least a portion of the received transaction data and/or other data is transmitted to processing unit 125 of rewards tracking system 110, that data indicating at least the monetary value of the attempted transaction by cardholder 145, referred to hereinafter as the purchase amount data. In an exemplary embodiment, processing unit 125 of rewards tracking system 110 converts the purchase amount data into at least a portion of a reward unit (point) using a predetermined computation, for instance, every dollar equals X reward unit(s), in 525. Next, processing unit 125 retrieves data stored in memory unit 130 indicating the balance of rewards account 310, 410. Processing unit 125 then determines whether the balance of rewards account 310, 410 is equal to or greater than the amount of pointa representing the converted purchase amount, in 530. If it is determined that the balance is equal to or greater than the converted purchase amount, then processing unit 125 transmits data to processing unit 115 indicating transaction authorization and processing unit 115 in turn transmits data indicating transaction authorization to the respective one of the plurality of merchants 140 a . . . 140 n, in 535. Processing unit 115 and/or processing unit 125 then adjusts the balance of reward account 310, 410 to reflect the converted converted amount which data is stored in memory unit 130, in 540. For example, the balance of reward account 310, 410 is decreased by an amount equal to the amount of points representing the purchase amount. If processing unit 125 determines that the balance of reward account 310, 410 is less than the converted purchase amount, then processing unit 125 and/or processing unit 115 determines whether at least one other payment method is available to cover at least a portion of the transaction amount, for instance, whether cardholder 145 has an associated credit account and/or an associated debit account that has a sufficient credit line and/or cash, respectively, in 545. In an exemplary embodiment, the associated credit account and/or the associated debit account is financial account 305. As will be appreciated by a person having ordinary skill in the art, data regarding accounts other than or in addition to financial account 305 can be retrieved and evaluated by processing unit 115 and/or processing unit 125 for determining whether a sufficient credit line and/or cash is available. In an exemplary embodiment, in order to determine whether at least one other payment method is available, processing unit 115 and/or processing unit 125 determines the difference between the balance of reward account 310, 410 and the converted purchase amount (referred to hereinafter as the �difference amount�). After determining the difference amount, processing unit 115 and/or processing unit 125 determines whether financial account 305 has an open credit line and/or cash that is greater than or equal to the difference amount, for example, upon retrieving data stored in memory unit 120. If financial account 305 has a sufficient open credit line and/or balance, then processing unit 115 transmits data indicating transaction authorization to the respective one of the plurality of merchants 140 a . . . 140 n, in 555. Processing unit 115 and/or processing unit 125 then adjusts the balance of reward account 310 to reflect the purchase amount, in 560. For example, the balance of reward account 310, 410 is decreased to zero or negative reward units predetermined by one or more business rules. The difference amount is credited or debited from financial account 305 depending on whether a credit line or cash, respectively, was used to fund part or all of the purchase amount, in 570. If financial account 305 has both a credit line and cash, then both can be used if need be in order to fund the purchase amount. If financial account 305 does not have a sufficient open credit line and/or cash, processing unit 115 searches for other accounts associated with cardholder 145 and if one or more such accounts are located, data regarding the account(s) is retrieved from memory unit 120 for locating another potential source for funding the difference amount. If no such account is located by processing unit 115 or if one or more accounts are located but do not have a sufficient credit line or cash, alone or in combination, processing unit 115 transmits data indicating that the transaction has been denied to the respective one of the plurality of merchants 140 a . . . 140 n, in 550. On the other hand, if one or more other accounts are located by processing unit 115, processing unit 115 transmits data to the respective one of the plurality of merchants 140 a . . . 140 n indicating approval of the transaction, in 555. Depending on the purchase amount, the balance of the reward account balance is decreased, for example, to zero or negative reward units, in 560. Further, the credit line and/or cash of the one or more other accounts, for instance, financial account 305, is increased and/or decreased, respectively, to fund the difference amount, 570. The respective one of the plurality of merchants 140 a . . . 140 n receives transaction authorization data or transaction denial data from processing unit 115 via credit/debit network 135 and consummates or does not consummate, respectively, the transaction with cardholder 145. As will be appreciated by a person having ordinary skill in the art, regardless whether conventional magnetic stripe 215 or reward magnetic stripe 220 is read at the respective merchant 140 a . . . 140 n, the merchant's experience is the same and hence the use of reward magnetic stripe 220 by cardholder 145 to make a purchase and the subsequent processing is transparent to the respective merchant. Alternatively, rewards account 310, 410 can have a balance equal to an amount of money earned from a rewards and cash back program. For example, for every predetermined amount that cardholder 145 spends using financial account 305 or for predetermined transactions whether using conventional magnetic stripe 215 or otherwise, a predetermined percentage of the amount of the purchase is deposited into rewards account 310, 410. Accounts other than account 305 can also be linked thereto so that cardholder 145 earns additional reward units or cash back. The accumulated cash in rewards account 310, 410 can be redeemed by cardholder 145 and the transaction can be processed in the same manner as described herein for redeeming points. The present application is not limited to rewards account 310, 410 being associated with accumulated reward units and cash back. Rather, other rewards, incentives or the like can be accumulated and redeemed by using reward magnetic stripe 220 such as credits, savings, certificates, changing membership status, for example, gold membership status to platinum membership status in a tiered product and special servicing, for example, a cardholder always gets a live telephone associate or the use of a specialized rewards planner. In an alternative embodiment of the present application, as opposed to data indicating account number(s) being stored on conventional magnetic stripe 215 and reward magnetic stripe 220, the magnetic stripes are encoded with data used by processing unit 115 to determine the respective account number, for instance, by utilizing a look-up table or the like stored in memory unit 120 and/or memory unit 130. In a further alternative embodiment of the present application, data indicating the same account number is encoded on conventional magnetic stripe 215 and reward magnetic stripe 220. However, at least one of the plurality of data fields associated with each of the magnetic stripes is encoded with data used by processing unit 115 to determine whether to access financial account 305 or rewards account 310, 410, for instance, by utilizing a look-up table or the like stored in memory unit 120 and/or memory unit 130. The embodiments described above are illustrative examples of the present application and it should not be construed that the present application is limited to these particular embodiments. Various changes and modifications may be effected by one skilled in the art without departing from the spirit or scope of the invention as defined in the appended claims. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7080776 *Feb 15, 2005Jul 25, 2006First Data CorporationTransaction card assemblies and methodsUS7367504 *Feb 15, 2006May 6, 2008First Data CorporationTransaction card assemblies and methodsUS7506804 *May 27, 2005Mar 24, 2009U.S. Bancorp Licensing, Inc.System and method for an integrated payment and reward cardUS7591419Aug 1, 2006Sep 22, 2009HSBC Card Services Inc.User selectable functionality facilitatorUS7784685Apr 26, 2007Aug 31, 2010United Services Automobile Association (Usaa)Secure cardUS7959076 *Apr 26, 2007Jun 14, 2011United Services Automobile Association (Usaa)Secure cardUS8038236Aug 24, 2007Oct 18, 2011Homag Holzbearbeitungssysteme AgDevice for patterning workpiecesUS8109436Apr 26, 2007Feb 7, 2012United Services Automobile Association (Usaa)Secure cardUS8157165Jul 10, 2009Apr 17, 2012HSBC Card Services Inc.User selectable functionality facilitatorUS8162208Feb 27, 2009Apr 24, 2012HSBC Card Services Inc.Systems and methods for user identification string generation for selection of a functionUS8376225Nov 11, 2011Feb 19, 2013United Services Automobile Association (Usaa)Secure cardWO2006068854A2 *Dec 7, 2005Jun 29, 2006Kenneth AlgieneTransaction card assemblies and methodsWO2010036915A2 *Sep 25, 2009Apr 1, 2010Visa International Service AssociationReal-time statement credits and notifications* Cited by examinerClassifications U.S. Classification235/380, 235/493International ClassificationG07F7/02, G06Q20/00, G06Q30/00, G06K19/08Cooperative ClassificationG06Q30/0216, G06Q30/0238, G06Q30/0226, G06K19/08, G06Q20/02, G07F7/025, G06Q30/02, G06Q20/342, G06Q30/0236, G06Q30/0215European ClassificationG06Q30/02, G06Q20/02, G06Q20/342, G06Q30/0216, G06Q30/0215, G06Q30/0226, G06Q30/0238, G06Q30/0236, G06K19/08, G07F7/02ELegal EventsDateCodeEventDescriptionJan 14, 2010FPAYFee paymentYear of fee payment: 4Jun 14, 2006ASAssignmentOwner name: CAPITAL ONE FINANCIAL CORPORATION, VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROSENBLATT, CHARLES AARON;FOX, ERIC;REEL/FRAME:017793/0307;SIGNING DATES FROM 20050617 TO 20050701Dec 18, 2003ASAssignmentOwner name: CAPITAL ONE FINANICAL CORPORATION, VIRGINIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:RETTENMYER, JESSICA ANN;GREENBERG, ROBERT JEROME;JAIN, CHITRA;REEL/FRAME:014834/0574Effective date: 20031204RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google