Universal payment protection
A system for and method of providing payment protection upon the occurrence of trigger events. The system and method include an account, which may be associated with a credit card or other financial product. An accountholder may select trigger events and associated benefits. Upon the occurrence of a trigger event, the issuing entity will evaluate whether the accountholder is entitled to receive an associated benefit. Each benefit is intended to address at least one payment obligation. For example, an account may include payment protection in the form of automatic payment of minimum monthly credit card fees should the accountholder involuntarily become unemployed.
Latest JPMorgan Chase Bank, N.A. Patents:
- Method and system for code maintenance
- Method and system for actionable smart monitoring of error messages
- System and method implementing a design system review tool
- METHOD AND SYSTEM FOR AUTOMATED MASKING OF TARGETED INFORMATION IN RESUMES
- Systems and methods for wayfinding in hazardous environments
The present invention generally relates to a system for and method of protecting entities with financial obligations. More particularly, the invention relates to a single account equipped with the ability to handle multiple financial obligations when certain trigger events occur.
DESCRIPTION OF RELATED ARTThe present application incorporates by reference in their entireties the following patents and pending patent applications: U.S. Pat. No. 6,615,190 to Slater entitled “Sponsor-Funded Stored Value Card”, Pending U.S. patent application Ser. No. 10/268,763 to Slater entitled “Sponsor Funded Stored Value Card”, U.S. Pat. No. 6,615,189 to Phillips et al. entitled “Debit Purchasing Of Stored Value Card For Use By And/Or Delivery To Others”, U.S. patent application Ser. No. 10/681,148 to Ilijasic et al. entitled “System and Method for Insuring Financial Accounts”, and U.S. patent application Ser. No. 10/681,148 to Ilijasic et al. entitled “System And Method For Insuring Financial Accounts”.
SUMMARY OF THE INVENTIONAccording to an embodiment of the present invention, a system for and method of relieving an entity (e.g., an individual, a family, a business) from at least one payment obligation are disclosed. The embodiment includes receiving information relating to the entity and deciding whether to issue an account to the entity. The embodiment also includes issuing an account to the entity in response to the step of deciding. The embodiment further includes receiving data, the data being associated with at least one of the entity and the account. The data include: first information reflecting a trigger circumstance, the first information defining a potential future situation, and second information reflecting a benefit, the benefit being intended to address at least one payment obligation, where the payment obligation is not initially associated with the account. The embodiment further includes processing at least a portion of the data using at least one probabilistic computation, the probabilistic computation including at least one financial assessment associated with the trigger circumstance. The embodiment further includes receiving an indication that a trigger circumstance has occurred. The embodiment further includes comparing information in the indication to account information associated with the entity. The embodiment further includes determining, based on the account information associated with the entity and consistent with the data received from the entity, that the entity is entitled to the benefit. The embodiment further includes providing the benefit to the entity in accordance with the account information associated with the entity.
Various optional features of the above embodiment include the following. The embodiment may include a line of credit as the benefit. The line of credit may be intended to address any payment obligation. The line of credit may be restricted. The embodiment may include restricting who may receive funds from the line of credit. The line of credit may be intended for use against a financial obligation arising from a financial product. The method may include disposing of the benefit. The disposing may include debt deferment, debt suspension, debt cancellation, or debt forgiveness. The trigger event may be a loss of employment, divorce, disability, hospitalization, medical treatment, family leave, judicial proceedings, tax events, natural disasters, call to duty, fire, flood, marriage, child birth, child adoption, retirement, or death. The payment obligation may be a loan (e.g., mortgage), bill (e.g., health insurance bill, life insurance bill, rent, utility bill, hospital bill, credit card bill, car insurance bill), car payment (e.g., payment on a car loan or lease), retirement savings, penalty, fine, attorney fees, tax, other type of lease, line of credit, letter of credit payment, or child support. The embodiment may include a financial product such as a credit card, a stored value card, a demand deposit account, a letter of credit, or a line of credit. The embodiment may include a web page accessible by the entity, where the step of receiving data selected by the entity occurs via the website. The embodiment may include conveying to the entity, via the website, information reflecting at least one fee received from the entity. The embodiment may further comprise receiving an application from the entity, the application including the information relating to the entity, and accepting the application. The embodiment may further include receiving consideration. The consideration may include at least one fee received from the entity, at least a portion of the fee being associated with the benefit. The portion of the at least one fee associated with the benefit may include a flat fee, a lump sum fee, a percentage of a periodic obligation, a percentage of an outstanding debt, or a percentage of an average monthly balance. The consideration may include the entity obtaining an account. No compensation may be received in response to the step of issuing.
The embodiment may include receiving data selected by the entity. Such data, being associated with the account, may include third information reflecting a second trigger circumstance, the third information defining a potential future situation, and fourth information reflecting a second benefit, the second benefit being intended to address at least one payment obligation. Such an embodiment may further include receiving a request, the request indicating that a trigger circumstance has occurred, and comparing information in the request to account information associated with the entity. Such an embodiment may further include determining, based on the account information associated with the entity and consistent with the data received from the entity, that the entity is entitled to a triggered benefit, the triggered benefit being the benefit or the second benefit, and providing the triggered benefit to the entity in accordance with the account information associated with the entity.
The invention, both as to its structure and operation together with the additional objects and advantages thereof are best understood through the following description of exemplary embodiments of the present invention when read in conjunction with the accompanying drawings.
According to an embodiment of the present invention a universal clearinghouse account for payment protection is disclosed. The account is “universal” in the sense that it may be used to protect payment in any of a number of obligations, not limited to debts or obligations associated with the bank that issues the account. Thus, for example, the account may be used to defer a minimum monthly payment on a credit card that is not associated with the account. Such a deferral may be accomplished by issuing a line of credit to the accountholder, where the line of credit may only be used to pay minimum monthly payments on a particular credit card not associated with the account. Obligations (not limited to debts) that may be covered by the invention include, by way of non-limiting example: mortgage payments, secured and unsecured loans and lines of credit (e.g., business or consumer loans), education, credit cards (even credit cards not directly associated with the account or with the financial entity), vehicle payments (e.g., vehicle loans and vehicle leases), vehicle insurance, rent, lease, utilities (e.g., electricity, water, gas), retirement savings (e.g., 401k), penalties, fines, attorney fees, taxes, child support payments, hospital services, and any combination thereof. Any of these payments may be protected even if not initially associated with the account or financial institution. The account may include a credit card or line of credit, but is not limited to accounts that include such products.
According to certain embodiments of the present invention, a single account may provide payment protection for a plurality of financial obligations. Moreover, such embodiments may provide payment protection for obligations that are not initially associated with the account. By way of non-limiting example, certain embodiments of the present invention may include an account with a first bank that provides protection for: the minimum monthly payment on a credit card associated with a second bank, a mortgage payment where the mortgage is held by a third bank, a monthly payment into a 401K savings plan associated with a fourth bank, a car loan payment where the car loan is held by a fifth bank, and so on. In short, certain embodiments of the present invention may provide payment protection for any financial obligation whatsoever, regardless as to whether such obligation is associated with the account that provides the protection.
Note that embodiments of the present invention are not limited to submission of the application by the entity. For example, in certain embodiments of the present invention, the application may be submitted by a third-party, such as, by way of non-limiting example, a mortgage holder.
The account associated with an embodiment of the present invention may be a pre-existing account, in which case an application will already be on record. For example, the account may be associated with a mortgage, loan, or other pre-existing financial product associated with the entity. Alternately, an entity may apply for an account by telephone, in person, mail, email or internet. An entity may first be offered an opportunity to obtain an account according to an embodiment of the present invention by solicitation through mail, telephone, email, or any other advertisement technique such as billboard, television ad, or print ad. For telephonic signup, an entity may be solicited by telephone, or the entity may initiate the contact him or herself by dialing a telephone number that has been provided by any of the above-referenced advertisement techniques, for example. For mail signup, the entity may fill out a form and return it in a pre-paid envelope. The entity may obtain such a form, by way of non-limiting example, via its inclusion with a bill or other communication associated with a pre-existing account. For internet-based signup, the entity may visit a webpage and fill out a form. A link to such a webpage may appear on any content website or may be included in an emailed solicitation.
Once the entity (or other party) has submitted an application, the issuing bank determines whether it will accept 120 the application. Acceptance involves conventional risk-determination techniques, such as checking the applicant's credit. Further, the issuing bank may check its own records for the applicant should the applicant already be a customer of the issuing bank. Part of the determination typically involves screening the applicant according to normal screening procedures associated with any financial products that form part of the account. For example, for an embodiment of the present invention that includes a credit card, the acceptance process would typically include a screening of applicants similar or identical to a screening of applicants that would precede issuing such a credit card that is not associated with an embodiment of the present invention. For an embodiment of the present invention that includes a savings account only, the process will typically include the screening that an applicant would undergo upon application for a standard savings account. In sum, the financial product or products associated with an embodiment of the present invention typically define, in part, the screening process that an applicant will undergo. As discussed further below, such an initial screening process may be independent from a secondary screening process that is associated with requesting trigger events and their corresponding benefits.
Once the application is accepted, the customer may select trigger events and associated benefits 130. Note that in certain embodiments of the present invention, the accountholder may choose trigger events and associated benefits contemporaneously with his or her application submission 110. Trigger events generally initiate payment protection in accordance with certain embodiments of the present invention. Such events include, by way of non-limiting example, involuntary loss of employment, divorce, bankruptcy, disability, death judicial proceedings, tax events, natural disasters, and hospitalization. The accountholder may select trigger events from a list of possibilities that are displayed to the accountholder via, by way of non-limiting example, the interne, email, traditional mail, or telephone. Alternately, or in addition, the customer may define a trigger event him or herself. The customer may select any number of trigger events.
Benefits available according to certain embodiments of the present invention include deferring mandatory payments (e.g., monthly minimum payments) for a certain amount of time and without incurring interest, and/or extending one or more lines of credit (which may be done automatically by, e.g., via wire transfer to an account, adding credit to a credit card, or by adding to or distributing a stored value card). The type of protection invoked upon a trigger event may depend on the particular type of trigger event itself. Benefits may survive death of the accountholder.
Other types of benefits include one or more lines of credit. Such lines of credit may be limited to certain merchants by, for example, making the money available on the card associated with the account and limiting the card for use with particular merchants via a merchant code. Alternately, or in addition, certain embodiments of the invention may extend a generic line of credit, such that a trigger event causes a line of credit of a particular amount to be extended for any use whatsoever. In either the limited or generic case, a line of credit may be automatically entered onto the balance of a card associated with the account such as a credit or stored value card. Lines of credit extended as benefits according to certain embodiments of the present inventions may be drawn upon to retire up to a certain number of full or partial periodic payment obligations and/or full or partial debt balances.
A benefit may include a line of credit specifically targeted to paying obligations associated with a financial product that does not form part of the universal payment protection account. That is, an accountholder may possess a financial instrument, such as a credit card, that is not part of an account associated with an embodiment of the present invention. Such a financial product is referred to herein as an “outside financial product.” Such an outside financial product may have a payment obligation associated with it, such as a minimum monthly payment for a credit card. A benefit according to an embodiment of the present invention may include a line of credit that is specifically configured to pay obligations associated with outside financial products. In the example of a outside financial product credit card, a benefit may be a line of credit that covers the minimum monthly payments. Such a line of credit may be restricted for payment of that credit card only.
Note that embodiments of the present invention may be used to protect payment obligations for any of a variety of outside financial products such as, by way of non-limiting example, mortgages, loans such as car loans, savings accounts such as 401k accounts, and credit cards. Such line of credit benefits may be unrestricted, or may be restricted for use against any financial obligation including financial obligations associated with any financial product, whether an outside financial product or not.
Note also that payment protection of an outside financial product survives transfer of that outside financial product to another entity. For example, if an outside mortgage is protected, protection will survive the mortgage holder selling the mortgage to another entity. This is unlike e.g., prior art mortgage protection services where the mortgage protection is provided by the same entity that holds the mortgage.
Each trigger event is generally associated with at least one benefit. Likewise, each benefit is generally associated with at least one trigger event. As an example of a trigger event and benefit pair, certain embodiment of the present invention may include payment holidays. For example, embodiments of the present invention may offer the entity a set of certain predetermined days on which the entity may declare that a trigger event has occurred. A set of such predetermined days may typically, but not necessarily, include federal holidays. Thus, for example, once the entity selects such a set of days as part of selecting trigger events (e.g., at step 130), that entity may use any of the selected days (e.g., Veteran's Day) to declare that a trigger event has occurred. The entity may further select (e.g., at step 130) and eventually receive a benefit associated with such a trigger event. Such a benefit may include any of the benefits discussed herein. Alternately, or in addition, the entity may select a reprieve from an obligation for a limited time (e.g., a payment holiday). Such a reprieve may constitute an interest-free line of credit that automatically extends to the obligation that the entity has selected to be the recipient of the payment holiday.
Typically, the issuing bank calculates a value for each trigger event and associated benefit pair. Such a value is the result of an actuarial analysis of the trigger event, benefit, and accountholder information. The value may be calculated using standard actuarial charts, such as those prepared by or associated with the Society of Actuaries or the Social Security Administration, known to those of skill in the art. Such values generally represent an expected value of the trigger event and benefit pair. Once the issuing bank arrives at a value, it may price the associated payment protection.
Payment protection pricing may be determined as an actuarially-determined expected value plus an additional charge. The additional charge may include consideration of, by way of non-limiting example, administrative costs, marketing costs, competitive analysis, etc. Payment schemes that take into account both an actuarial value and an additional charge include, by way of non-limiting example, a flat monthly fee, a lump-sum fee, a percentage of a monthly obligation (e.g., a percentage of a monthly mortgage payment), a percentage of a total outstanding debt (e.g., a percentage of an entire mortgage), a percentage of an average monthly balance, or any combination of the preceding. Once a total fee is determined using actuarial analysis and other considerations 140, it is included 150 in a bill to the accountholder.
The issuing bank then compares 230 the reported trigger event with those subscribed to by the accountholder and decides whether the accountholder is entitled to one or more benefits. The decision process may further involve inquiries of the accountholder or other parties. By way of non-limiting example, in the event of hospitalization, the accountholder, hospital, or insurer, for example, may be required to produce evidence of hospitalization to the issuing bank. Evidence may take the form of a receipt, insurance report, police report, or other indicia of hospitalization. Evidence may be conveyed automatically, without the participation of the accountholder. In the hospitalization example, the issuing bank may gather receipts, insurance reports, or police reports directly from, respectively, the hospital, the insurer, or the police, without the involvement of the accountholder. In general, additional evidence required by the issuing bank may include, by way of non-limiting example, receipts, official reports, death certificates, court records or orders, police records, sworn statements, verified statements, other statements, telephonic verification with the accountholder or a third party, emailed verification with the accountholder or a third party, and written verification by the accountholder or a third party. Once the issuing bank decides that the accountholder is entitled to one or more benefits, it will provide 240 the same to the accountholder.
The accountholder or other benefit recipient may receive the benefit automatically. Exemplary techniques for such automatic transfer include, by way of non-limiting example, check, direct deposit, or wire transfer to the accountholder or directly to the party to whom the obligation is due, or by addition to or distribution of a stored value card. Automatic transfer may include activation of a stored value card, e.g., using the techniques taught in U.S. Pat. No. 6,615,190 to Slater entitled “Sponsor-Funded Stored Value Card.”
At step 250, the benefit is optionally disposed of. That is, certain embodiments of the present invention cancel or suspend without interest the debt incurred by accepting a benefit. The disposition of a debt arising from a benefit may be predetermined based on the terms and conditions of the debt protection agreement options selected and actively in place. That is, selecting a disposal option may occur as part of selecting benefits and trigger events. In certain embodiments, a line of credit specifically configured for payment of obligations associated with an outside financial product serves to effectively defer payment of those obligations until such time that repayment of the line of credit is due. However, certain embodiments may dispose of the benefit by entirely forgiving debt arising from the line of credit. In such embodiments, the disposal of the benefit may serve to effectively cancel outside financial product payment obligation altogether.
The accountholder may use the web page to select the length of time that deferment will last should the accountholder select a deferment benefit. The length of time may be an absolute length of time, e.g., measured in days, a relative length of time, e.g., until the accountholder resumes employment, or a combination of both, e.g., the longer of when the accountholder resumes employment or 100 days. The user may select a length of time from a list or may be able to enter a length of time into a field particularly designed for such a feature. Note that selection of a length of time is not limited to selection via a website; an accountholder may perform such selection telephonically, by way of regular mail, or through any other communication technique.
Embodiments of the present invention may calculate payment options in response to the accountholder's request. That is, when an accountholder selects a trigger event and benefit pair, the issuing bank typically performs an actuarial computation and calculates an associated fee (140 of
The account holder may specify a maximum monthly fee, and the issuing bank may calculate coverage options (trigger events and associated benefits) that are available for that amount. The issuing bank may store a list of the accountholder's payment obligations of which it is aware, and draw from such a list in response to the accountholder's request. For example, the accountholder may specify that he or she is willing to pay $5 per month for some type of payment protection. The issuing bank may determine all trigger event and benefit pairs that are available to that accountholder for such a fee. Alternately, or in addition, the accountholder may narrow the field of trigger events and/or benefits that are subject to this feature. For example, the accountholder may be interested in all deferments that are available for $5 per month on any of a variety of payment obligations. The issuing bank may then offer the accountholder a choice of payment obligations that it may defer for a fee of $5 per month. Note that presentation of trigger events and/or benefits is not limited to presentation via a website. The issuing bank may convey such options to an accountholder telephonically, by way of regular mail, or through any other communication technique.
The accountholder may specify on the website a hierarchy of debts to be paid in order upon certain trigger events. That is, where the accountholder selects debt cancellation as a benefit, he or she may further specify which debts should be cancelled in order. Specifying the order of debt cancellation may be accomplished via the web page or any other communication channel, such as telephone, mail, or email.
The accountholder may designate individuals that are to receive funds via stored value cards or other techniques upon certain trigger events. More generally, certain embodiments of the present invention allow persons other than the accountholder to receive benefits. Such persons may be specified on the web page during account signup (e.g., 130 of
The web page may include a trigger event reporting feature 350. Such a feature may include a list of trigger events that the accountholder has selected and been approved for. The accountholder may use the reporting feature to report trigger events to the issuing bank. By way of non-limiting example, the reporting feature may allow the accountholder to click on a particular trigger event, which will cause a separate dialog screen to appear in which the accountholder may present details of the trigger event. As discussed above in reference to
The web page may be used to check on the status of any outstanding trigger events. By way of non-limiting example, the web page may include a list of trigger events about which the accountholder has notified the issuing bank. The accountholder may click on a listed pending trigger event, by way of non-limiting example, in order to receive information about the issuing bank's processing status of the trigger event. Such information may include an identification of additional information required by the issuing bank. It may further include an estimated time remaining until the accountholder receives the associated benefit.
Certain embodiments of the present invention may incorporate trigger events that are activated by an individual other than the accountholder. By way of non-limiting example, one such trigger event my be an accountholder's spouse involuntarily losing his or her job. As another example, hospitalization of an accountholder's child may trigger cancellation of debt associated with the accountholder. As yet another example, the accountholder may be a minor, who may receive a line of credit restricted for use against a college savings plan in response to the divorce of a parent accountholder. In this latter example, the debt arising from the line of credit may be cancelled in disposing of the benefit. In general, a benefit may protect payment obligations of the accountholder, the person associated with the trigger event, or a third party.
Note that embodiments of the present invention do not provide insurance in the traditional sense, in that they do not pay claims. Instead, certain embodiments of the present invention extend lines of credit. Repayment on these lines of credit may be canceled or deferred.
Advantages of certain embodiments of the present invention include the following. One advantage is a removal of the need for a separate consolidation contract (and signature, in the event of activation) for each separate debt or obligation. Another advantage is that the issuing bank becomes associated with many of the accountholder's obligations. Yet another advantage is that the debt protection liability does not transfer to an owner or investor in the accountholder's obligation because it does not attach to the accountholder's obligation instrument as an amendment. Therefore no prior approval or additional agreements must be made with an owner of or investor in the accountholder's obligation.
The terminology used herein is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the present invention. Unless defined otherwise, all technical, financial and scientific terms used herein have the same meanings as commonly understood by one of ordinary skill in the art to which this invention belongs. As used throughout this disclosure, the singular forms “a,” “an,” and “the” include plural reference unless the context clearly dictates otherwise.
Claims
1. A computer implemented method of relieving an entity from at least one future payment obligation, the computer implemented method comprising:
- receiving, at a web page, information relating to the entity;
- deciding whether to issue an account to the entity;
- issuing an account to the entity in response to the step of deciding, wherein the entity uses the account for purchases from third parties;
- receiving data provided by the entity at a web page, the data being associated with at least one of the entity and the account, the data comprising: first information reflecting a trigger circumstance, the first information defining a potential future situation, and second information reflecting a line of credit intended to address at least one payment obligation; wherein the payment obligation is not initially associated with the account and not in existence at a time of issuance of the account, and wherein the payment obligation is owed to a third party;
- processing, using a programmed computer, at least a portion of the data using at least one actuarial computation, the actuarial computation reflecting an expected value of the line of credit;
- receiving from the entity at least one payment associated with the trigger circumstance and the line of credit, the at least one payment providing the entity with the ability to receive the line of credit upon occurrence of the trigger circumstance, the at least one payment comprising the expected value of the line of credit and at least one additional fee;
- receiving an indication that a trigger circumstance has occurred;
- comparing information in the indication to account information associated with the entity;
- determining, based on the account information associated with the entity and consistent with the data received from the entity, that the entity is entitled to the line of credit; and
- providing the line of credit to the entity in accordance with the account information associated with the entity.
2. The method of claim 1 wherein the line of credit is intended to address any payment obligation.
3. The method of claim 1 further comprising restricting use of the line of credit.
4. The method of claim 3 wherein the restricting comprises restricting who receives funds from the line of credit.
5. The method of claim 1 wherein the line of credit is intended for use against a financial obligation arising from a financial product.
6. The method of claim 1 wherein the trigger event is selected from the group consisting of: loss of employment, divorce, disability, hospitalization, medical treatment, family leave, natural disaster, judicial proceeding, tax event, call to duty, fire, flood, marriage, child birth, child adoption, retirement, and death.
7. The method of claim 1 wherein the at least one payment obligation is selected from the group consisting of: loan payment, insurance bill, rent, utility bill, hospital bill, mortgage payment, credit card bill, retirement savings, car payment, penalty, fine, attorney fee, tax, lease, line of credit, letter of credit payment, and child support.
8. The method of claim 1 wherein the account comprises at least one financial product selected from the group consisting of: a credit card, a benefit card, a stored value card, a letter of credit, and a line of credit.
9. The method of claim 1 further comprising:
- receiving data selected by the entity, the data being associated with the account, the data comprising: third information reflecting a second trigger circumstance, the third information defining a potential future situation, and fourth information reflecting a second line of credit, the second line of credit being intended to address at least one payment obligation;
- receiving a request, the request indicating that a trigger circumstance has occurred;
- comparing information in the request to account information associated with the entity;
- determining, based on the account information associated with the entity and consistent with the data received from the entity, that the entity is entitled to a triggered benefit, the triggered benefit being selected from the group consisting of: the line of credit and the second line of credit; and
- providing the triggered benefit to the entity in accordance with the account information associated with the entity.
10. A system for relieving an entity from at least one future payment obligation, the system comprising:
- a computer configured to receive information relating to the entity;
- an account associated with the entity, wherein the account is usable by the entity to make purchases from third parties;
- a web page configured to receive data selected by the entity, the data being associated with the account, the data comprising: first information reflecting a trigger circumstance, the first information defining a potential future situation, and second information reflecting a line of credit being intended to address at least one payment obligation, wherein the payment obligation is not initially associated with the account and not in existence at a time of issuance of the account, and wherein the payment obligation is owed to a third party;
- a computer configured to process at least a portion of the data using at least one actuarial computation, the actuarial computation reflecting an expected value of the line of credit;
- means for receiving from the entity at least one payment associated with the trigger circumstance and the line of credit, the at least one payment providing the entity with the ability to receive the line of credit upon occurrence of the trigger circumstance, the at least one payment comprising the expected value of the line of credit and at least one additional fee;
- a web page configured to receive a request, the request indicating that a trigger circumstance has occurred;
- a computer configured to compare information in the request to account information associated with the entity;
- a computer configured to determine, based on the account information associated with the entity and consistent with the data received from the entity, that the entity is entitled to the line of credit; and
- means for providing the line of credit to the entity in accordance with the account information associated with the entity.
11. The system of claim 10 wherein the line of credit is intended to address any payment obligation.
12. The system of claim 10 wherein use of the line of credit is restricted.
13. The system of claim 12 wherein the restricting comprises restricting who fray receives funds from the line of credit.
14. The system of claim 10 wherein the line of credit is intended for use against a financial obligation arising from a financial product.
15. The system of claim 10 wherein the trigger event is selected from the group consisting of: loss of employment, divorce, disability, hospitalization, medical treatment, family leave, judicial proceeding, tax event, natural disaster, call to duty, fire, flood, marriage, child birth, child adoption, retirement, and death.
16. The system of claim 10 wherein the at least one payment obligation is selected from the group consisting of: loan payment, insurance bill, rent, utility bill, hospital bill, mortgage payment, credit card bill, retirement savings, car payment, penalty, fine, attorney fee, tax, lease, line of credit, letter of credit payment, and child support.
17. The system of claim 10 further comprising at least one financial product selected from the group consisting of: a credit card, a benefit card, a stored value card, a letter of credit, and a line of credit, wherein the account comprises the at least one financial product.
18. The system of claim 10 further comprising:
- a computer configured to receive data selected by the entity, the data being associated with the account, the data comprising: third information reflecting a second trigger circumstance, the third information defining a potential future situation, and fourth information reflecting a second line of credit, the second line of credit being intended to address at least one payment obligation;
- a web page configured to receive a request, the request indicating that a trigger circumstance has occurred;
- a computer configured to compare information in the request to account information associated with the entity;
- a computer configured to determine, based on the account information associated with the entity and consistent with the data received from the entity, that the entity is entitled to a triggered benefit, the triggered benefit being selected from the group consisting of: the line of credit and the second line of credit; and
- means for providing the triggered benefit to the entity in accordance with the account information associated with the entity.
19. The system of claim 10, further comprising:
- means for receiving an application from the entity, the application comprising information relating to the entity; and
- means for accepting the application.
20. A system for of relieving an entity from at least one future payment obligation, the system comprising:
- means for receiving an application from the entity;
- means for accepting the application;
- means for issuing an account to the entity in response to said accepting, wherein the entity uses the account for purchases from third parties;
- means for receiving data selected by the entity, the data being associated with the account, the data comprising: first information reflecting a trigger circumstance, the first information defining a potential future situation, and second information reflecting a line of credit, the line of credit being intended to address at least one payment obligation, wherein the at least one payment obligation is not initially associated with the account and wherein the payment obligation is owed to a third party;
- means for processing at least a portion of the data using at least one actuarial computation, the actuarial computation reflecting an expected value of the line of credit;
- means for receiving from the entity at least one fee associated with the trigger circumstance and the line of credit, the at least one fee providing the entity with the ability to receive the line of credit upon occurrence of the trigger circumstance, the at least one fee comprising the expected value of the line of credit and at least one additional fee;
- means for receiving a request, the request indicating that a trigger circumstance has occurred;
- means for comparing information in the request to account information associated with the entity;
- means for determining, based on the account information associated with the entity and consistent with the data received from the entity that the entity is entitled to the line of credit; and
- means for providing the line of credit to the entity in accordance with the account information associated with the entity.
21. A computer implemented method of relieving an entity from at least one future payment obligation, the computer implemented method comprising:
- receiving, at a web page, information relating to the entity;
- deciding whether to issue an account to the entity;
- issuing an account to the entity in response to the step of deciding, wherein the entity uses the account for purchases from third parties;
- receiving data provided by the entity at a web page, the data being associated with at least one of the entity and the account, the data comprising: first information reflecting a trigger circumstance, the first information defining a potential future situation, and second information reflecting a line of credit intended to address at least one payment obligation, wherein the payment obligation is not initially associated with the account and wherein the payment obligation is owed to a third party, and wherein the trigger circumstance is selected from the group consisting of: loss of employment, divorce, disability, hospitalization, medical treatment, family leave, natural disaster, judicial proceeding, tax event, call to duty, fire, flood, marriage, child birth, child adoption, retirement, and death;
- processing, using a programmed computer, at least a portion of the data using at least one actuarial computation, the actuarial computation reflecting an expected value of the line of credit;
- receiving from the entity at least one payment associated with the trigger circumstance and the line of credit, the at least one payment providing the entity with the ability to receive the line of credit upon occurrence of the trigger circumstance, the at least one payment comprising the expected value of the line of credit and at least one additional fee;
- receiving an indication that a trigger circumstance has occurred;
- comparing information in the indication to account information associated with the entity;
- determining, based on the account information associated with the entity and consistent with the data received from the entity, that the entity is entitled to the line of credit; and
- providing the line of credit to the entity in accordance with the account information associated with the entity.
| 3634669 | January 1972 | Soumas et al. |
| 3713235 | January 1973 | Roberts |
| 3946206 | March 23, 1976 | Darjany |
| 4047033 | September 6, 1977 | Malmberg et al. |
| 4058220 | November 15, 1977 | Torongo |
| D248203 | June 20, 1978 | Morse |
| 4130881 | December 19, 1978 | Haessler et al. |
| 4465206 | August 14, 1984 | Sorel et al. |
| 4545838 | October 8, 1985 | Minkus et al. |
| 4582985 | April 15, 1986 | Lofberg |
| 4614861 | September 30, 1986 | Pavlov et al. |
| 4634845 | January 6, 1987 | Riley |
| 4643452 | February 17, 1987 | Chang et al. |
| 4689478 | August 25, 1987 | Hale et al. |
| 4700055 | October 13, 1987 | Kashkashian, Jr. |
| 4746787 | May 24, 1988 | Suto et al. |
| 4750119 | June 7, 1988 | Cohen et al. |
| 4752676 | June 21, 1988 | Leonard et al. |
| 4754418 | June 28, 1988 | Hara |
| 4766293 | August 23, 1988 | Boston |
| 4766539 | August 23, 1988 | Fox |
| 4789928 | December 6, 1988 | Fujisaki |
| 4822985 | April 18, 1989 | Boggan et al. |
| 4831242 | May 16, 1989 | Englehardt |
| 4831526 | May 16, 1989 | Luchs |
| 4837422 | June 6, 1989 | Dethloff et al. |
| 4868376 | September 19, 1989 | Lessin et al. |
| 4870259 | September 26, 1989 | Boggan et al. |
| 4882675 | November 21, 1989 | Nichtberger et al. |
| 4897533 | January 30, 1990 | Lyszczarz |
| D305887 | February 6, 1990 | Nishimura |
| 4906826 | March 6, 1990 | Spencer |
| 4908521 | March 13, 1990 | Boggan et al. |
| 4923288 | May 8, 1990 | Allen et al. |
| 4928001 | May 22, 1990 | Masada |
| 4941090 | July 10, 1990 | McCarthy |
| 4943707 | July 24, 1990 | Boggan |
| 4953085 | August 28, 1990 | Atkins |
| 4954985 | September 4, 1990 | Yamazaki |
| 4961142 | October 2, 1990 | Elliott et al. |
| 4968873 | November 6, 1990 | Dethloff et al. |
| 4975840 | December 4, 1990 | DeTore et al. |
| 4978401 | December 18, 1990 | Bonomi |
| 4992940 | February 12, 1991 | Dworkin |
| 5025372 | June 18, 1991 | Burton et al. |
| 5049728 | September 17, 1991 | Rovin |
| 5055662 | October 8, 1991 | Hasegawa |
| 5080748 | January 14, 1992 | Bonomi |
| 5095194 | March 10, 1992 | Barbanell |
| 5117355 | May 26, 1992 | McCarthy |
| 5146068 | September 8, 1992 | Ugawa et al. |
| 5175416 | December 29, 1992 | Mansvelt |
| 5177342 | January 5, 1993 | Adams |
| 5180901 | January 19, 1993 | Hiramatsu |
| 5185697 | February 9, 1993 | Jacobs et al. |
| 5191522 | March 2, 1993 | Bosco et al. |
| 5192947 | March 9, 1993 | Neustein |
| 5202286 | April 13, 1993 | Nakatani |
| 5202826 | April 13, 1993 | McCarthy |
| 5206488 | April 27, 1993 | Teicher |
| 5206803 | April 27, 1993 | Vitagliano |
| 5214700 | May 25, 1993 | Pinkas et al. |
| 5218631 | June 8, 1993 | Katz |
| 5247190 | September 21, 1993 | Friend et al. |
| 5276311 | January 4, 1994 | Hennige |
| 5287268 | February 15, 1994 | McCarthy |
| 5287269 | February 15, 1994 | Dorrough et al. |
| 5297026 | March 22, 1994 | Hoffman |
| 5311594 | May 10, 1994 | Penzias |
| 5326959 | July 5, 1994 | Perazza |
| 5326960 | July 5, 1994 | Tannenbaum |
| 5328809 | July 12, 1994 | Holmes et al. |
| 5339239 | August 16, 1994 | Manabe et al. |
| 5349633 | September 20, 1994 | Katz |
| 5350906 | September 27, 1994 | Brody et al. |
| 5359183 | October 25, 1994 | Skodlar |
| 5361062 | November 1, 1994 | Weiss et al. |
| 5365575 | November 15, 1994 | Katz |
| 5383113 | January 17, 1995 | Knight |
| 5397881 | March 14, 1995 | Mannik |
| 5399502 | March 21, 1995 | Friend et al. |
| 5401827 | March 28, 1995 | Holmes et al. |
| RE34915 | April 25, 1995 | Nichtberger et al. |
| 5424524 | June 13, 1995 | Ruppert et al. |
| 5450477 | September 12, 1995 | Amarant et al. |
| 5453601 | September 26, 1995 | Rosen |
| 5455407 | October 3, 1995 | Rosen |
| 5457305 | October 10, 1995 | Akel et al. |
| 5459306 | October 17, 1995 | Stein et al. |
| 5465206 | November 7, 1995 | Hilt et al. |
| 5466919 | November 14, 1995 | Hovakimian |
| 5471669 | November 28, 1995 | Lidman |
| 5477038 | December 19, 1995 | Levine et al. |
| 5477040 | December 19, 1995 | Lalonde |
| 5479494 | December 26, 1995 | Clitherow |
| 5482139 | January 9, 1996 | Rivalto |
| 5483444 | January 9, 1996 | Malark |
| 5483445 | January 9, 1996 | Pickering |
| 5500514 | March 19, 1996 | Veeneman et al. |
| 5503891 | April 2, 1996 | Marshall et al. |
| 5511114 | April 23, 1996 | Stimson et al. |
| 5512654 | April 30, 1996 | Holmes et al. |
| 5513102 | April 30, 1996 | Auriemma |
| 5521363 | May 28, 1996 | Tannenbaum |
| 5530232 | June 25, 1996 | Taylor |
| 5530235 | June 25, 1996 | Stefik et al. |
| 5537314 | July 16, 1996 | Kanter |
| 5544086 | August 6, 1996 | Davis et al. |
| 5544246 | August 6, 1996 | Mandelbaum et al. |
| 5553120 | September 3, 1996 | Katz |
| 5577109 | November 19, 1996 | Stimson et al. |
| 5578808 | November 26, 1996 | Taylor |
| 5581064 | December 3, 1996 | Riley et al. |
| 5585787 | December 17, 1996 | Wallerstein |
| 5590038 | December 31, 1996 | Pitroda |
| 5592560 | January 7, 1997 | Deaton et al. |
| 5604542 | February 18, 1997 | Dedrick |
| 5608785 | March 4, 1997 | Kasday |
| 5612868 | March 18, 1997 | Off |
| 5619558 | April 8, 1997 | Jheeta |
| 5621787 | April 15, 1997 | McKoy et al. |
| 5621812 | April 15, 1997 | Deaton et al. |
| 5637845 | June 10, 1997 | Kolls |
| 5638457 | June 10, 1997 | Deaton et al. |
| 5642279 | June 24, 1997 | Stone |
| 5642485 | June 24, 1997 | Deaton et al. |
| 5644723 | July 1, 1997 | Deaton et al. |
| 5644727 | July 1, 1997 | Atkins |
| 5649114 | July 15, 1997 | Deaton et al. |
| 5649117 | July 15, 1997 | Landry |
| 5649118 | July 15, 1997 | Carlisle et al. |
| 5653914 | August 5, 1997 | Holmes et al. |
| 5659741 | August 19, 1997 | Eberhardt |
| 5664110 | September 2, 1997 | Green et al. |
| 5664157 | September 2, 1997 | Takahira et al. |
| 5665953 | September 9, 1997 | Mazzamuto |
| 5672678 | September 30, 1997 | Holmes et al. |
| 5675607 | October 7, 1997 | Alesio et al. |
| 5675662 | October 7, 1997 | Deaton et al. |
| 5677955 | October 14, 1997 | Doggett et al. |
| 5684291 | November 4, 1997 | Taskett |
| 5687322 | November 11, 1997 | Deaton et al. |
| 5689100 | November 18, 1997 | Carrithers et al. |
| 5689650 | November 18, 1997 | McClelland et al. |
| 5692132 | November 25, 1997 | Hogan |
| 5696907 | December 9, 1997 | Tom |
| 5699528 | December 16, 1997 | Hogan |
| 5703344 | December 30, 1997 | Bezy et al. |
| 5704046 | December 30, 1997 | Hogan |
| 5705798 | January 6, 1998 | Tarbox |
| 5708422 | January 13, 1998 | Blonder et al. |
| 5710458 | January 20, 1998 | Iwasaki |
| 5710886 | January 20, 1998 | Christensen et al. |
| 5710887 | January 20, 1998 | Chelliah |
| 5710889 | January 20, 1998 | Clark et al. |
| 5715399 | February 3, 1998 | Bezos |
| 5717925 | February 10, 1998 | Harper et al. |
| 5721768 | February 24, 1998 | Stimson et al. |
| 5721781 | February 24, 1998 | Deo et al. |
| 5726884 | March 10, 1998 | Sturgeon et al. |
| 5727153 | March 10, 1998 | Powell |
| 5728998 | March 17, 1998 | Novis et al. |
| 5729693 | March 17, 1998 | Holda-Fleck |
| 5734154 | March 31, 1998 | Jachimowicz et al. |
| 5734838 | March 31, 1998 | Robinson |
| 5736728 | April 7, 1998 | Matsubara |
| 5737421 | April 7, 1998 | Audebert |
| 5740549 | April 1998 | Reilly et al. |
| 5742775 | April 21, 1998 | King |
| 5745049 | April 28, 1998 | Akiyama et al. |
| 5745706 | April 28, 1998 | Wolfberg et al. |
| 5749075 | May 5, 1998 | Toader et al. |
| 5760381 | June 2, 1998 | Stich et al. |
| 5765138 | June 9, 1998 | Aycock et al. |
| 5765141 | June 9, 1998 | Spector |
| 5770843 | June 23, 1998 | Rose et al. |
| 5770849 | June 23, 1998 | Novis et al. |
| 5774870 | June 30, 1998 | Storey |
| 5777305 | July 7, 1998 | Smith et al. |
| 5777306 | July 7, 1998 | Masuda |
| 5777903 | July 7, 1998 | Piosenka et al. |
| 5778067 | July 7, 1998 | Jones et al. |
| 5787156 | July 28, 1998 | Katz |
| 5787404 | July 28, 1998 | Fernandez-Holman |
| 5789733 | August 4, 1998 | Jachimowicz et al. |
| 5790636 | August 4, 1998 | Marshall |
| 5794207 | August 11, 1998 | Walker |
| 5798950 | August 25, 1998 | Fitzgerald |
| 5799087 | August 25, 1998 | Rosen |
| 5802176 | September 1, 1998 | Audebert |
| 5805719 | September 8, 1998 | Pare et al. |
| 5806042 | September 8, 1998 | Kelly et al. |
| 5806044 | September 8, 1998 | Powell |
| 5806045 | September 8, 1998 | Biorge |
| 5807627 | September 15, 1998 | Friend et al. |
| 5809478 | September 15, 1998 | Greco |
| 5814796 | September 29, 1998 | Benson et al. |
| 5815657 | September 29, 1998 | Williams et al. |
| 5815658 | September 29, 1998 | Kuriyama |
| 5819234 | October 6, 1998 | Slavin et al. |
| 5819237 | October 6, 1998 | Garman |
| 5826243 | October 20, 1998 | Musmanno et al. |
| 5832457 | November 3, 1998 | O'Brien |
| 5832488 | November 3, 1998 | Eberhardt |
| 5835061 | November 10, 1998 | Stewart |
| 5835576 | November 10, 1998 | Katz |
| 5839113 | November 17, 1998 | Federau et al. |
| 5845259 | December 1, 1998 | West et al. |
| 5845260 | December 1, 1998 | Nakano et al. |
| 5852811 | December 22, 1998 | Atkins |
| 5852812 | December 22, 1998 | Reeder |
| 5857079 | January 5, 1999 | Claus et al. |
| 5857175 | January 5, 1999 | Day |
| 5857709 | January 12, 1999 | Chock |
| 5859419 | January 12, 1999 | Wynn |
| 5864609 | January 26, 1999 | Cross et al. |
| 5864828 | January 26, 1999 | Atkins |
| 5864830 | January 26, 1999 | Armetta et al. |
| RE36116 | February 23, 1999 | McCarthy |
| 5870718 | February 9, 1999 | Spector |
| 5870721 | February 9, 1999 | Norris |
| 5875437 | February 23, 1999 | Atkins |
| 5883377 | March 16, 1999 | Chapin, Jr. |
| 5883810 | March 16, 1999 | Franklin et al. |
| 5884271 | March 16, 1999 | Pitroda |
| 5884278 | March 16, 1999 | Powell |
| 5884285 | March 16, 1999 | Atkins |
| 5887065 | March 23, 1999 | Audebert |
| 5890138 | March 30, 1999 | Godin et al. |
| 5890140 | March 30, 1999 | Clark et al. |
| H1794 | April 6, 1999 | Claus |
| 5897620 | April 27, 1999 | Walker et al. |
| 5897621 | April 27, 1999 | Boesch et al. |
| 5905246 | May 18, 1999 | Fajkowski |
| 5907350 | May 25, 1999 | Nemirofsky |
| 5907828 | May 25, 1999 | Meyer et al. |
| 5911135 | June 8, 1999 | Atkins |
| 5911136 | June 8, 1999 | Atkins |
| 5914472 | June 22, 1999 | Foladare et al. |
| 5920629 | July 6, 1999 | Rosen |
| 5920844 | July 6, 1999 | Hotta et al. |
| 5920847 | July 6, 1999 | Kolling et al. |
| 5923734 | July 13, 1999 | Taskett |
| 5926800 | July 20, 1999 | Baronowski et al. |
| 5930217 | July 27, 1999 | Kayanuma |
| 5931764 | August 3, 1999 | Freeman et al. |
| 5933817 | August 3, 1999 | Hucal |
| 5937068 | August 10, 1999 | Audebert |
| 5940811 | August 17, 1999 | Norris |
| 5946669 | August 31, 1999 | Polk |
| 5952641 | September 14, 1999 | Korshun |
| 5953423 | September 14, 1999 | Rosen |
| 5953710 | September 14, 1999 | Fleming |
| 5955961 | September 21, 1999 | Wallerstein |
| 5956695 | September 21, 1999 | Carrithers et al. |
| 5963648 | October 5, 1999 | Rosen |
| 5963925 | October 5, 1999 | Kolling et al. |
| 5970479 | October 19, 1999 | Shepherd |
| 5970480 | October 19, 1999 | Kalina |
| 5974399 | October 26, 1999 | Giuliani et al. |
| RE36365 | November 2, 1999 | Levine et al. |
| 5984180 | November 16, 1999 | Albrecht |
| 5984191 | November 16, 1999 | Chapin, Jr. |
| 5987434 | November 16, 1999 | Libman |
| 5988509 | November 23, 1999 | Taskett |
| 5991413 | November 23, 1999 | Arditti et al. |
| 5991743 | November 23, 1999 | Irving et al. |
| 5991748 | November 23, 1999 | Taskett |
| 5991750 | November 23, 1999 | Watson |
| 5999596 | December 7, 1999 | Walker et al. |
| 6000608 | December 14, 1999 | Dorf |
| 6000832 | December 14, 1999 | Franklin et al. |
| 6002383 | December 14, 1999 | Shimada |
| 6003762 | December 21, 1999 | Hayashida |
| 6004681 | December 21, 1999 | Epstein et al. |
| 6006988 | December 28, 1999 | Behrmann et al. |
| 6009415 | December 28, 1999 | Shurling et al. |
| 6014636 | January 11, 2000 | Reeder |
| 6014638 | January 11, 2000 | Burge et al. |
| 6014645 | January 11, 2000 | Cunningham |
| 6014749 | January 11, 2000 | Gloor et al. |
| 6016482 | January 18, 2000 | Molinari et al. |
| 6016954 | January 25, 2000 | Abe et al. |
| 6019284 | February 1, 2000 | Freeman et al. |
| 6021189 | February 1, 2000 | Vu |
| 6026370 | February 15, 2000 | Jermyn |
| 6029139 | February 22, 2000 | Cunningham et al. |
| 6029144 | February 22, 2000 | Barrett et al. |
| 6029890 | February 29, 2000 | Austin |
| 6032136 | February 29, 2000 | Brake, Jr. et al. |
| 6032859 | March 7, 2000 | Muehlberger et al. |
| 6036099 | March 14, 2000 | Leighton |
| 6038292 | March 14, 2000 | Thomas |
| 6038552 | March 14, 2000 | Fleischl et al. |
| 6041315 | March 21, 2000 | Pollin |
| 6044360 | March 28, 2000 | Picciallo |
| 6045042 | April 4, 2000 | Ohno |
| 6047067 | April 4, 2000 | Rosen |
| 6047268 | April 4, 2000 | Bartoli et al. |
| 6049463 | April 11, 2000 | O'Malley et al. |
| 6049773 | April 11, 2000 | McCormack et al. |
| 6049782 | April 11, 2000 | Gottesman et al. |
| 6058378 | May 2, 2000 | Clark et al. |
| 6064985 | May 16, 2000 | Anderson |
| 6065675 | May 23, 2000 | Teicher |
| 6068183 | May 30, 2000 | Freeman et al. |
| 6070067 | May 30, 2000 | Nguyen et al. |
| 6070147 | May 30, 2000 | Harms et al. |
| 6070153 | May 30, 2000 | Simpson |
| 6076068 | June 13, 2000 | DeLapa et al. |
| 6076072 | June 13, 2000 | Libman |
| 6078888 | June 20, 2000 | Johnson, Jr. |
| 6078891 | June 20, 2000 | Riordan et al. |
| 6091817 | July 18, 2000 | Bertina et al. |
| 6092056 | July 18, 2000 | Tull, Jr. et al. |
| 6095412 | August 1, 2000 | Bertina et al. |
| 6095416 | August 1, 2000 | Grant et al. |
| 6098053 | August 1, 2000 | Slater |
| 6105011 | August 15, 2000 | Morrison, Jr. |
| 6105865 | August 22, 2000 | Hardesty |
| 6109525 | August 29, 2000 | Blomqvist et al. |
| 6112191 | August 29, 2000 | Burke |
| 6115458 | September 5, 2000 | Taskett |
| 6119097 | September 12, 2000 | Ibarra |
| 6119103 | September 12, 2000 | Basch et al. |
| 6119107 | September 12, 2000 | Polk |
| 6119932 | September 19, 2000 | Maloney et al. |
| 6122623 | September 19, 2000 | Garman |
| 6128598 | October 3, 2000 | Walker et al. |
| 6128599 | October 3, 2000 | Walker et al. |
| 6129274 | October 10, 2000 | Suzuki |
| 6129572 | October 10, 2000 | Feldman et al. |
| 6134309 | October 17, 2000 | Carson |
| 6134536 | October 17, 2000 | Shepherd |
| 6138917 | October 31, 2000 | Chapin, Jr. |
| 6145741 | November 14, 2000 | Wisdom et al. |
| 6148297 | November 14, 2000 | Swor et al. |
| 6161096 | December 12, 2000 | Bell |
| 6163770 | December 19, 2000 | Gamble et al. |
| 6164533 | December 26, 2000 | Barton |
| 6167385 | December 26, 2000 | Hartley-Urquhart |
| 6169975 | January 2, 2001 | White et al. |
| 6173267 | January 9, 2001 | Cairns |
| 6182048 | January 30, 2001 | Osborn et al. |
| 6182894 | February 6, 2001 | Hackett et al. |
| 6186793 | February 13, 2001 | Brubaker |
| 6189787 | February 20, 2001 | Dorf |
| 6192113 | February 20, 2001 | Lorsch |
| 6195644 | February 27, 2001 | Bowie |
| 6202053 | March 13, 2001 | Christiansen et al. |
| RE37122 | April 3, 2001 | Levine et al. |
| 6213392 | April 10, 2001 | Zuppichich |
| 6223143 | April 24, 2001 | Weinstock et al. |
| 6227447 | May 8, 2001 | Campisano |
| 6243688 | June 5, 2001 | Kalina |
| 6260758 | July 17, 2001 | Blumberg |
| 6263316 | July 17, 2001 | Khan et al. |
| 6265977 | July 24, 2001 | Vega et al. |
| 6278981 | August 21, 2001 | Dembo et al. |
| 6295344 | September 25, 2001 | Marshall |
| 6295522 | September 25, 2001 | Boesch |
| 6298336 | October 2, 2001 | Davis et al. |
| 6308268 | October 23, 2001 | Audebert |
| 6315196 | November 13, 2001 | Bachman |
| 6324524 | November 27, 2001 | Lent et al. |
| 6330546 | December 11, 2001 | Gopinathan et al. |
| 6336099 | January 1, 2002 | Barnett et al. |
| 6338048 | January 8, 2002 | Mori |
| 6341724 | January 29, 2002 | Campisano |
| 6343743 | February 5, 2002 | Lamla |
| 6345261 | February 5, 2002 | Feidelson |
| 6345766 | February 12, 2002 | Taskett et al. |
| 6349291 | February 19, 2002 | Varma |
| 6360954 | March 26, 2002 | Barnardo |
| 6366220 | April 2, 2002 | Elliott |
| 6373969 | April 16, 2002 | Adler |
| 6374230 | April 16, 2002 | Walker et al. |
| 6377669 | April 23, 2002 | Walker et al. |
| 6385591 | May 7, 2002 | Mankoff |
| 6385594 | May 7, 2002 | Lebda et al. |
| 6386444 | May 14, 2002 | Sullivan |
| 6397202 | May 28, 2002 | Higgins et al. |
| 6402039 | June 11, 2002 | Freeman et al. |
| 6405182 | June 11, 2002 | Cuervo |
| 6422459 | July 23, 2002 | Kawan |
| 6422462 | July 23, 2002 | Cohen |
| 6424029 | July 23, 2002 | Giesler |
| 6429927 | August 6, 2002 | Borza |
| 6434259 | August 13, 2002 | Hamid et al. |
| D462477 | September 3, 2002 | Osborne |
| 6446210 | September 3, 2002 | Borza |
| 6450407 | September 17, 2002 | Freeman et al. |
| 6463039 | October 8, 2002 | Ricci et al. |
| 6467684 | October 22, 2002 | Fite et al. |
| 6473500 | October 29, 2002 | Risafi et al. |
| 6481125 | November 19, 2002 | Pokrasoff |
| 6484144 | November 19, 2002 | Martin et al. |
| 6484148 | November 19, 2002 | Boyd |
| 6484428 | November 26, 2002 | Greenwald et al. |
| D466929 | December 10, 2002 | Haas |
| D467271 | December 17, 2002 | Haas |
| D467272 | December 17, 2002 | Haas |
| 6498861 | December 24, 2002 | Hamid et al. |
| D468789 | January 14, 2003 | Arnold et al. |
| 6505095 | January 7, 2003 | Kolls |
| 6505168 | January 7, 2003 | Rothman et al. |
| 6505780 | January 14, 2003 | Yassin et al. |
| 6529880 | March 4, 2003 | McKeen et al. |
| D474235 | May 6, 2003 | Haas |
| 6557750 | May 6, 2003 | Druse et al. |
| 6557766 | May 6, 2003 | Leighton |
| 6560578 | May 6, 2003 | Eldering |
| 6561657 | May 13, 2003 | Schofield |
| 6567786 | May 20, 2003 | Bibelnieks et al. |
| 6567821 | May 20, 2003 | Polk |
| 6574603 | June 3, 2003 | Dickson et al. |
| 6581839 | June 24, 2003 | Lasch et al. |
| D476681 | July 1, 2003 | Al Amri |
| D477359 | July 15, 2003 | Haas |
| 6601040 | July 29, 2003 | Kolls |
| 6601761 | August 5, 2003 | Katis |
| 6609111 | August 19, 2003 | Bell |
| RE38255 | September 23, 2003 | Levine et al. |
| 6615189 | September 2, 2003 | Phillips et al. |
| 6615190 | September 2, 2003 | Slater |
| 6625582 | September 23, 2003 | Richman et al. |
| 6631849 | October 14, 2003 | Blossom |
| 6641049 | November 4, 2003 | Luu |
| 6641050 | November 4, 2003 | Kelley et al. |
| 6671673 | December 30, 2003 | Baseman et al. |
| D485573 | January 20, 2004 | Li |
| 6675127 | January 6, 2004 | LaBlanc et al. |
| 6675149 | January 6, 2004 | Ruffin et al. |
| 6693544 | February 17, 2004 | Hebbecker |
| 6732919 | May 11, 2004 | Macklin et al. |
| 6742704 | June 1, 2004 | Fitzmaurice et al. |
| 6745938 | June 8, 2004 | Sullivan |
| 6757660 | June 29, 2004 | Canada et al. |
| 6757710 | June 29, 2004 | Reed |
| D495736 | September 7, 2004 | Scharf |
| 6793135 | September 21, 2004 | Ryoo |
| 6802008 | October 5, 2004 | Ikefuji et al. |
| 6805287 | October 19, 2004 | Bishop |
| 6856973 | February 15, 2005 | Bott |
| 6865547 | March 8, 2005 | Brake, Jr. et al. |
| 6868426 | March 15, 2005 | Mankoff |
| 6876971 | April 5, 2005 | Burke |
| D505450 | May 24, 2005 | Lauer et al. |
| 6895383 | May 17, 2005 | Heinrich |
| 6895386 | May 17, 2005 | Bachman et al. |
| 6901372 | May 31, 2005 | Helzerman |
| 6912502 | June 28, 2005 | Buddle et al. |
| 6970830 | November 29, 2005 | Samra et al. |
| 6978369 | December 20, 2005 | Wheeler et al. |
| 6999943 | February 14, 2006 | Johnson et al. |
| 7006992 | February 28, 2006 | Packwood |
| 7051925 | May 30, 2006 | Schwarz, Jr. |
| 7062031 | June 13, 2006 | Becerra et al. |
| 7072864 | July 4, 2006 | Brake, Jr. et al. |
| 7072909 | July 4, 2006 | Polk |
| 7089503 | August 8, 2006 | Bloomquist et al. |
| 7092905 | August 15, 2006 | Behrenbrinker et al. |
| 7092916 | August 15, 2006 | Diveley et al. |
| 7104443 | September 12, 2006 | Paul et al. |
| 7107249 | September 12, 2006 | Dively et al. |
| 7113914 | September 26, 2006 | Spielmann et al. |
| D533220 | December 5, 2006 | Graves et al. |
| 7165049 | January 16, 2007 | Slater |
| D538349 | March 13, 2007 | Hollands |
| 7216091 | May 8, 2007 | Blandina et al. |
| 7225155 | May 29, 2007 | Polk |
| 7243839 | July 17, 2007 | Beck et al. |
| 7249092 | July 24, 2007 | Dunn et al. |
| 7252223 | August 7, 2007 | Schofield |
| D551705 | September 25, 2007 | Mershon |
| 7266524 | September 4, 2007 | Butcher, III |
| 7295999 | November 13, 2007 | Simon et al. |
| 7315843 | January 1, 2008 | Diveley et al. |
| 7346562 | March 18, 2008 | Inoue et al. |
| 7346567 | March 18, 2008 | Weeks |
| 7373304 | May 13, 2008 | Pletz et al. |
| 7392222 | June 24, 2008 | Hamilton et al. |
| 7392224 | June 24, 2008 | Bauer et al. |
| 7406426 | July 29, 2008 | Pletz et al. |
| 20010011227 | August 2, 2001 | Ashery et al. |
| 20010011243 | August 2, 2001 | Dembo et al. |
| 20010027389 | October 4, 2001 | Beverina et al. |
| 20010027441 | October 4, 2001 | Wankmueller |
| 20010034647 | October 25, 2001 | Marks et al. |
| 20010034682 | October 25, 2001 | Knight et al. |
| 20010037315 | November 1, 2001 | Saliba et al. |
| 20010044293 | November 22, 2001 | Morgan |
| 20010047332 | November 29, 2001 | Gonen-Friedman et al. |
| 20010047342 | November 29, 2001 | Cuervo |
| 20010054003 | December 20, 2001 | Chien et al. |
| 20010056398 | December 27, 2001 | Scheirer |
| 20020019793 | February 14, 2002 | Frattalone |
| 20020019803 | February 14, 2002 | Muller |
| 20020026418 | February 28, 2002 | Koppel et al. |
| 20020032609 | March 14, 2002 | Wilkman |
| 20020046089 | April 18, 2002 | Zorn |
| 20020046255 | April 18, 2002 | Moore et al. |
| 20020062235 | May 23, 2002 | Wahlbin et al. |
| 20020065720 | May 30, 2002 | Carswell et al. |
| 20020077964 | June 20, 2002 | Brody et al. |
| 20020077978 | June 20, 2002 | O'Leary et al. |
| 20020082990 | June 27, 2002 | Jones |
| 20020091572 | July 11, 2002 | Anderson et al. |
| 20020091631 | July 11, 2002 | Usui |
| 20020095365 | July 18, 2002 | Slavin et al. |
| 20020099586 | July 25, 2002 | Bladen et al. |
| 20020104878 | August 8, 2002 | Seifert et al. |
| 20020111916 | August 15, 2002 | Coronna et al. |
| 20020116271 | August 22, 2002 | Mankoff |
| 20020116330 | August 22, 2002 | Hed et al. |
| 20020120627 | August 29, 2002 | Mankoff |
| 20020120642 | August 29, 2002 | Fetherston |
| 20020129221 | September 12, 2002 | Borgin et al. |
| 20020138409 | September 26, 2002 | Bass |
| 20020138418 | September 26, 2002 | Zarin et al. |
| 20020143703 | October 3, 2002 | Razvan et al. |
| 20020147662 | October 10, 2002 | Anderson |
| 20020156723 | October 24, 2002 | Lilly et al. |
| 20020165771 | November 7, 2002 | Walker et al. |
| 20020165820 | November 7, 2002 | Anvekar et al. |
| 20020169719 | November 14, 2002 | Dively et al. |
| 20020174016 | November 21, 2002 | Cuervo |
| 20020174018 | November 21, 2002 | Bunger et al. |
| 20020178025 | November 28, 2002 | Hansen et al. |
| 20020194081 | December 19, 2002 | Perkowski |
| 20030004828 | January 2, 2003 | Epstein |
| 20030009358 | January 9, 2003 | Greenfeld et al. |
| 20030018613 | January 23, 2003 | Oytac |
| 20030023549 | January 30, 2003 | Armes et al. |
| 20030028518 | February 6, 2003 | Mankoff |
| 20030033211 | February 13, 2003 | Haines et al. |
| 20030033246 | February 13, 2003 | Slater |
| 20030046249 | March 6, 2003 | Wu |
| 20030053609 | March 20, 2003 | Risafi et al. |
| 20030074290 | April 17, 2003 | Clore |
| 20030078881 | April 24, 2003 | Elliott et al. |
| 20030101119 | May 29, 2003 | Parsons et al. |
| 20030105672 | June 5, 2003 | Epstein et al. |
| 20030110111 | June 12, 2003 | Nalebuff et al. |
| 20030135462 | July 17, 2003 | Brake, Jr. et al. |
| 20030140004 | July 24, 2003 | O'Leary et al. |
| 20030144935 | July 31, 2003 | Sobek |
| 20030154125 | August 14, 2003 | Mittal et al. |
| 20030163403 | August 28, 2003 | Chen et al. |
| 20030163416 | August 28, 2003 | Kitajima |
| 20030172040 | September 11, 2003 | Kemper et al. |
| 20030195808 | October 16, 2003 | Brown et al. |
| 20030200143 | October 23, 2003 | Walker et al. |
| 20030200180 | October 23, 2003 | Phelan et al. |
| 20030204421 | October 30, 2003 | Houle et al. |
| 20030216947 | November 20, 2003 | Callen et al. |
| 20030216965 | November 20, 2003 | Libman |
| 20030229525 | December 11, 2003 | Callahan et al. |
| 20040024672 | February 5, 2004 | Brake, Jr. et al. |
| 20040030626 | February 12, 2004 | Libman |
| 20040039588 | February 26, 2004 | Libman |
| 20040059952 | March 25, 2004 | Newport et al. |
| 20040064402 | April 1, 2004 | Dreyer et al. |
| 20040093296 | May 13, 2004 | Phelan et al. |
| 20040093303 | May 13, 2004 | Picciallo |
| 20040098351 | May 20, 2004 | Duke |
| 20040103431 | May 27, 2004 | Davenport et al. |
| 20040107161 | June 3, 2004 | Tanaka et al. |
| 20040118914 | June 24, 2004 | Smith et al. |
| 20040122697 | June 24, 2004 | Becerra et al. |
| 20040128186 | July 1, 2004 | Breslin et al. |
| 20040193539 | September 30, 2004 | Sullivan |
| 20040215507 | October 28, 2004 | Levitt et al. |
| 20040243498 | December 2, 2004 | Duke |
| 20050021353 | January 27, 2005 | Aviles et al. |
| 20050021400 | January 27, 2005 | Postrel |
| 20050021457 | January 27, 2005 | Johnson et al. |
| 20050027649 | February 3, 2005 | Cech |
| 20050035192 | February 17, 2005 | Bonalle et al. |
| 20050071230 | March 31, 2005 | Mankoff |
| 20050075932 | April 7, 2005 | Mankoff |
| 20050077350 | April 14, 2005 | Courtion et al. |
| 20050091138 | April 28, 2005 | Awatsu |
| 20050102228 | May 12, 2005 | Srinivasan et al. |
| 20050108064 | May 19, 2005 | Castleman et al. |
| 20050108152 | May 19, 2005 | Tsoa-Lee et al. |
| 20050119979 | June 2, 2005 | Murashita |
| 20050125259 | June 9, 2005 | Annappindi |
| 20050135593 | June 23, 2005 | Becerra et al. |
| 20050171842 | August 4, 2005 | Tien et al. |
| 20050171898 | August 4, 2005 | Bishop et al. |
| 20050177508 | August 11, 2005 | Pembroke |
| 20050199705 | September 15, 2005 | Beck et al. |
| 20050234771 | October 20, 2005 | Register et al. |
| 20050251478 | November 10, 2005 | Yanavi |
| 20050269396 | December 8, 2005 | Schofield |
| 20050289044 | December 29, 2005 | Breslin et al. |
| 20060026092 | February 2, 2006 | Klein et al. |
| 20060036553 | February 16, 2006 | Gupta et al. |
| 20060047573 | March 2, 2006 | Mitchell et al. |
| 20060047589 | March 2, 2006 | Grau |
| 20060074794 | April 6, 2006 | Nespola |
| 20060085334 | April 20, 2006 | Murphy |
| 20060093123 | May 4, 2006 | Becerra et al. |
| 20060106696 | May 18, 2006 | Carlson |
| 20060116903 | June 1, 2006 | Becerra |
| 20060122918 | June 8, 2006 | Graboske et al. |
| 20060131869 | June 22, 2006 | Brignull |
| 20060136231 | June 22, 2006 | Thomas |
| 20060224480 | October 5, 2006 | Bent et al. |
| 20060242057 | October 26, 2006 | Velarde |
| 20080177659 | July 24, 2008 | Lacey et al. |
| 20090048972 | February 19, 2009 | Bierer et al. |
| 20090063202 | March 5, 2009 | Becerra et al. |
| 20090132312 | May 21, 2009 | Reinheimer et al. |
| 20090157437 | June 18, 2009 | Becerra et al. |
| 2293321 | June 1998 | CA |
| 0843292 | May 1998 | EP |
| 0855659 | July 1998 | EP |
| 959440 | November 1999 | EP |
| 2275654 | September 1994 | GB |
| 2376787 | December 2002 | GB |
| 2377071 | December 2002 | GB |
| 2377314 | January 2003 | GB |
| WO 94/29112 | December 1994 | WO |
| WO 97/41673 | November 1997 | WO |
| WO 98/59307 | December 1998 | WO |
| WO 99/05633 | February 1999 | WO |
| WO 99/54841 | October 1999 | WO |
| WO 01/18699 | March 2001 | WO |
| WO 01/69347 | September 2001 | WO |
| WO 01/69347 | September 2001 | WO |
| WO 2004/027564 | April 2004 | WO |
| WO 2004/040419 | May 2004 | WO |
| WO 2004/114641 | December 2004 | WO |
| WO 2005/043277 | May 2005 | WO |
| WO 2009/023817 | February 2009 | WO |
- 5500—FDIC General Counsel's Opinion No. 8—Stored Value Cards, 61 Fed. Reg. 40490, http://www.fdic.gov/regulations/laws/rules/5500-500.html, Aug. 2, 1996.
- Song, A Card That Asks For ID, TIme Magazine, Apr. 12, 2004, 1 page.
- A Store Card Issuer Looks for Lift from Electronic Gift Certificates, Credit Card News, Feb. 1, 1995, 2 pages.
- Hotchkiss, ATM's at the head of their class, Bank Marketing, vol. 29, No. 3, Mar. 1997, pp. 26-32.
- Edwards, ATMs The Hot New Media Buy, ABA Banking Journal, Mar. 1999, pp. 58, 60.
- Fickenscher, Amex Prepaid Offering is Latest Card for Firms Regarding Employees, American Banker, vol. 161, No. 151, Aug. 8, 1996, pp. 1-2.
- Neumann, An Enhanced Neural Network Technique for Software Risk Analysis, IEEE Transactions on Software Engineering, vol. 28, No. 9, Sep. 1, 2002, pp. 904-912.
- Associates First Capital Corporation, Hoover's Inc., The Industry Standard: The Newsmagazine of the Internet Economy, thestandard.net/companies/company-display, Apr. 6, 1999.
- Award Card Comparison, JA7922.
- Brehl, Banks issue cash-card pledge, The Toronto Star, Oct. 9, 1997, 1 page.
- Blockbuster running test of a stored value card, The American Banker, Sep. 1, 1995.
- Meece, Boatman's Prepaid Cards for Worker-Incentive Firm, American Banker, Jul. 2, 1996, p. 12.
- Boatmen's Floats Stored Value into the Employee Incentive Waters, Debit Card News, vol. 2, Issue 2, Jul. 16, 1996, 3 pages.
- CES/NaBANCO introduces stored value card technology blockbuster video is first merchant partner, Business Wire, Inc., Jan. 15, 1996.
- Card Based Award Systems, JA8309.
- CardEx Incentives, www.cardex.com, Apr. 6, 1999.
- CardFlash, Apr. 5, 2005.
- Vandenengel, Cards on the Internet: Advertising on a $3 Bill, Industry Intelligence, Feb. 1, 1995, pp. 46-48.
- Kutler, Cash Card Creator Looking Beyond Mondex, Feb. 9, 1995.
- Rosen, Cash Just Isn't Flexible Enough: Shops of the Future Will Only Take Cards, Daily Express, Technology Section, Feb. 10, 1995, 1 page.
- Bank, Cash, Check,Charge—What's Next?, Seattle Times, Mar. 6, 1995.
- Morgan et al., Categorizing Risks for Risk Ranking, vol. 20, No. 1, Jun. 22, 2005, pp. 49-58.
- Common electronic purse specifications, Business Requirements, Version 6.0, Dec. 1998.
- Guidotti, Comparing Environmental risks: A Consultative Approach to Setting Priorities at the Community Level, Public Health Rev 1994, vol. 22, Jun. 16, 2005, pp. 321-337.
- Britt, Competing in Auto Lending, America's Community Banker, vol. 5, No. 11, Nov. 1, 1996, pp. 33-37.
- Consortium created to manage common electronic purse specification, Cardtech Securtech, Chicago, www.visa.com/av/news/PRmisc051199.vhtml, May 11, 1999.
- Mobasher et al., Creating Adaptive Web Sites Through Usage-Based Clustering of URLs, Knowledge and Data Engineering Exchange Workshop, Chicago, IL and Los Alamitos, CA, 1999, pp. 19-25.
- Lamond, Credit Card Transactions Real World and Online, Paying By Credit Card-Real World and Online, http://www.virtualschool.edu/mon/ElectronicProperty/klamond/credit, printed Jul. 8, 2005, 17 pages.
- D.C. Area Safeway Stores Look for Increase in Sales Volume and Revenue with Cards, Card News, vol. 6, No. 25, Dec. 30, 1991, pp. 7-9.
- Piskora, Debit Cards Seen Poised for New Markets, American Banker, Credit/Debit/ATMs, Mar. 7, 1995, p. 16.
- E-Z Pass, Web page, http://www.ezpass.com-Disc—portNewYork.html, Nov. 12, 2001.
- E-Z Pass, Web page, http\\www.ezpass.com-Disc—ny—annual.html, Nov. 12, 2001.
- E-Z Pass, Web page, http:\\www.ezpass.com-frameMain.html, Nov. 12, 2001.
- E-Z Pass, Web page, http:\\www.ezpass.com-whatis.html, Nov. 12, 2001.
- Business Times, Electronic Purse Can Free You from ATM Drag, Business Times, www.btimes.co.za, printed Feb. 23, 2001, 1 page.
- Electronic Purse, SCIA (Smart Card Industry Association), About Smart Cards, www.scia.org, printed Feb. 23, 2001, 1 page.
- Sanchez-Klein, Electronic purse alliance planned, Computerworld Online News, Jul. 29, 1998, printed Feb. 23, 2001, 2 pages.
- Electronic purse card to be launched tomorrow, New Straits Times, News Clippings, Sep. 18, 1999, printed Feb. 23, 2001, 3 pages.
- First Data markets stored-value cards, Cards International, Jan. 30, 1996, p. 5.
- First USA—Activate Today and Get One Hour Free Calling Card Calls, Call 1-800-555-2535, First USA, 6 pages.
- First USA—Call 1(800)335-2453 To Receive One Free Hour of Domestic Long Distance Calling (No Strings Attached), First USA, 6 pages.
- First USA Platinum Connect, First USA Bank, First USA Promotional Mailing, Oct. 1997, 6 pages.
- First Union Issues Smart Cards to Fort Benning Recruits, CardFax, vol. 1999, No. 60, Mar. 26, 1999, 1 page.
- Norris, First data unit develops blockbuster cash card, Omaha World Hearld Sunrise Edition, Business Section, Jan. 19, 1996, p. 16.
- Frequently asked questions, ECARD, www.eregard.com, printed Sep. 23, 2001, 7 pages.
- Glossman, et al., Glossman, et al., Citicorp- Company Report.
- Machlis, Have it the smart way: Burger King program drives smart-card use, Computerworld, printed Feb. 23, 2001, 1 page.
- Here's the calling convience you asked for: 1-800-call-ATT . . . For All Calls, AT&T, Appendix A: For Card Carriers, 1999, 7 pages.
- Hoovers, General Mills, Inc. Corporate Profile relied upon to show the history of the company, http:/cobrands.hoovers.com/global/cobrands/proquest/history.xhtml?COID=10639, Jul. 12, 2005, 2 pages.
- How Is It Different?, JA8331.
- Konrad, IBM Has a Bunch of Unusual Ideas in 2003, www.philly.com, printed Jan. 21, 2004, posted on Jan. 13, 2004, 2 pages.
- Incenticard, Bellsouth, JA8329.
- Incentive Firms Find Debit Cards A Rewarding Experience (Off-line debit card issuers converge efforts with companies looking for effective incentives to boost employee productivity and to motivate individuals to buy their products), Debit Card News, Vol.
- Coulton, Incentives Field Moving to Card-Based Series 14, American Banker, Mar. 26, 1998, 3 pages.
- Introducing SpendingMoney(TM), Armetta: Marketing & Design Product Concept Report, Oct. 9, 1996, 15 pages.
- Introducing the First USA Platinum Connect Card, First USA Promotional Mailing, Dec. 1997, 2 pages.
- Key Bank Holiday Offer, http://www.key.com/swiftgift/home.html, printed Apr. 5, 1999.
- MailFrontier Survey Finds that Consumers Hold Financial Institutions Accountable for Online Identity Theft, www.mailfrontier.com, Palo Alto, CA, Nov. 2004.
- O'Connor, Maritz Gets MasterCard's Stamp of Approval, Business Travel News, Aug. 19, 1996, 2 pages.
- Meridian Award Cards, JA8251.
- Meridan Interoffice Memo, MeridiCard Enhancement-Floating Credit Limit, JA8354-JA8355, Aug. 2, 1989.
- Meridian-the leader in card marketing, JA8343.
- Meridicard vs. Debit Cards, JA7917.
- Clark, Mircosoft, Visa to Jointly Develop PC Electronic-Shopping Software, The Wall Street Journal, Nov. 9, 1994, WSJ B9.
- More Retailers Turn to Co-Branding, Chain Store Age Executive with Shopping Center Age, Feb. 1, 1995, 3 pages.
- Bogle, Mutual Funds at the Millennium: Fund Directors and Fund Myths, The Vanguard Group to the ′40 Act Institute of PLI (Practicing Law Institute), New York, NY, May 15, 2000, 15 pages.
- New 1-800-CALL-ATT Campaign Promotes One Number for All Calls, AT&T Marketing, News Release, www.att.com/press/0297/970217.csa.htm, Feb. 17, 1997, 2 pages.
- Schwab,Charles, Now 7 Ways For A better Total Return For Your Money; Schwat 1, The Inventor's Asset Management Account, Charles R. Schwab, Charles Schwab & Co., Inc., 16 pages.
- Dugas, Payroll May Ask: Paper of Plastic?, USA Today, 3B, Aug. 14, 2001, 1 page.
- Proton world and Europay to co-operate in creation of new CEPS-compliant e-purse application, Press Release 1999, Waterloo, Belgium, Jun. 28, 1999, 2 pages.
- Brown et al., Purchasing Card Magic: Eli Lilly Finds Accounts Payable Flying High With Plastic, Corporate Cashflow, vol. 15, No. 12, Nov. 1994, 2 pages.
- Purse Application for Cross Border Use in Euro, Cordis, Pace 1st 1999-11531 Pace, www.cordis.lu, printed Feb. 23, 2001, 3 pages.
- SK100 Smart Card Electronic Purse Balance Reader, SK100 Balance Reader, http://perso.wanadoo.fr, printed Feb. 23, 2001, 1 page.
- Miller, Section E.2.1: Kerberos Authentication and Authorization System, Project Athena, Cambridge, MA, Dec. 21, 1987, 39 pages.
- Souccar, Smart Cards: 1st Union Smard Card Pilot Enlists a Second Army Base, American Banker, Digital Frontiers, vol. 164, No. 61, Mar. 31, 1999, 3 pages.
- Smart Cards: Big Brother's Little Helpers, The Privacy Committee of New South Wales, No. 66, Aug. 1995.
- Smart card for loyalty and e-purse applications eclipses capability of conventional mag-stripe cards, Press Release, www.1.sib.com, Apr. 21, 1997, printed Feb. 23, 2001, 3 pages.
- SmartAxis: Load Cash on to your E-Purse Card, Supported Currencies and Schemes, www.smartaxis.co.uk, printed Feb. 23, 2001, 9 pages.
- Spurgin, Sopininmon! or What's Happening in the Retail Credit Card Environment, Credit World Journal, vol. 85, No. 4, Mar. 1, 1997, pp. 20-23.
- Lacker, Stored Value Cards: Costly Private Substitutions for Government Currency, Economic Quarterly, 1996, Economic Quarterly, v82, n3, p1(25), ISSN: 1069-7225, 17 pages.
- Lazarony, Stuck for a gift? Give a prepaid credit card, www.bankrate.com, Dec. 21, 1998, 1 page.
- Key, Swift Gift ‘Wows’ Internet Shoppers, PR Newswire, www.key.com/swiftgift/home.html, Dec. 2, 1998, 1 page.
- The Campus Card Conundrum, Card Technology, Journal ISSN: 1093-1279, p. 25+, Feb. 1998, pp. 1-8.
- The Electronic Purse Reaches the Car Park, http:\\docs.vircom.net/mobility/parking, printed Feb. 23, 2001, 2 pages.
- The Evolution of a New Consumerism, Chain Store Age, vol. 73, Jun. 1997, pp. 8-9.
- Stoughton, The Gift of Credit, www.washingtonpost.com/wp-srv/business, Dec. 14, 1998.
- Stuber, The electronic purse: An overview of recent development and issues, Bank of Canada, Technical Report No. 74, www.bankofcanada.ca, Jan. 1996, printed Feb. 23, 2001, 2 pages.
- Understanding the benefits: Smartcity offers a number of important benefits to both the card issuers and their customers, http://www.icl.com/smartcards/benefits.htm, printed Feb. 27, 2001, 2 pages.
- Langheinrich et al., Unintrusive Customization Techniques for Web Advertising, Computer Networks, vol. 31, 1999, pp. 1259-1272.
- Universal Card free lifetime membership extended 3 months, AT&T Marketing, www.att.com/press/0297/970217.csa.html, Dec. 4, 1990, 2 pages.
- Visa Cash—Where can I get it?, www.visa-asia.com/pd/cash/where.html, Feb. 23, 2001.
- Visa Cash, www.visa-asia.com/pd/cash/main.html, Feb. 23, 2001.
- Visa International And SERMEPA Announce Plans For Cross Border Visa Cash Based on CEPS, www.visa.com/av/news/praaamisc111699.vhtml, Nov. 16, 1999.
- Visa first to launch electornic purse load via GSM mobile phone, www.cellular.co.za, Johannesburg, ZA, printed Feb. 23, 2001, 4 pages.
- Visa releases visa cash electronic purse specifications based on CEPS, www.visa.com/av/news/PRaamisc042099.vhtml, San Francisco, Apr. 20, 1999.
- Hansell, Visa to unveil electronic purse cards, New York Times, printed Feb. 23, 2001, 2 pages.
- Welcome To Card Express CardEx website archived by web.archive on Oct. 31, 1996, http://web.archive.org/web/*/http://www.cardex.com, retrieve Oct. 18, 2003, 7 pages.
- Welcome To Card Express, The CardEx Incentive Card, as disclosed in the CardEx web site archived by web.archive.org on Feb. 7, 1998, http://web.archive.org/web/*/http://www.cardex.com, retrieve Oct. 18, 2003, 8 pages.
- Swiftgift, Welcome to Swiftgift, www.swiftgiftcard.com, Dec. 8, 1998, 10 pages.
- Machlis et al., Will Smart cards replace ATMS?, Computerworld, printed Feb. 23, 2001, 3 pages.
- Claessens, et al., A Tangled World Wide Web of Security Issues, First Monday, retrieved from the internet at http://www.firstmonday.org/issues/issue7—3/claesens, retrieved from the internet on Oct. 6, 2006.
- American Express Incentive Services, Incentive, Sep. 1996, p. 126.
- Hight, Jim, Consulting Services, www.strategies-tactics.com.
- Nora Wood, Corporate Spotlight, Incentive, Dec. 1997, 4 pages.
- Definition of Store-Value Card, Wikipedia, retrieved from the internet at http://en.wikipedia.org/wiki/Stored-value—card, retrieved from the internet on Apr. 16, 2007.
- Eight Keys to Making the Right Choice, Incentive, Dec. 1996, 9 pages.
- D. O'Mahony, Electronic Payment System, 1997, Artech House, XP002137255, p. 7-11.
- Exclusively Yours From Maritz . . . The MasterCard Card Ultimate Incentive, Incentive, Oct. 1995, 3 pages.
- Block, First Data Subsidiary Creates Payroll Card for the Bankless, LexisNexis Academic, Credit/Debit/ATMs, p. 10, Mar. 21, 1997.
- Hamey, Kenneth, Home Asset Management Accounts Link Mortgages Equity Lines.
- Judy Quinn, Incentive Cards Explained, Incentive, Dec. 1995, 5 pages.
- Vincent Alonzo, Incentive Marketing . . . Three If By Smart Card, Incentive Sep. 1995, p. 11.
- Incentive gift Card: Another way to give of choice!, Incentive, Aug. 1995, 2 pages.
- LexisNexis Academic, Debit Card Innovation, vol. XXXV, No. 5, p. 2, May 1997.
- LexisNexis Academic, Debit Cards: Payroll Card Ups Fees, Future Banker, p. 18, Oct. 6, 1997.
- LexisNexis Academic, NTS' TransPay Debit Card Helps Remote and Unbanked Employees Get Funds Quicker, Financial News, Mar. 18, 1997.
- O'Conner, Maritz Gets MasterCard's Stamp of Approval, Business Travel News, Aug. 19, 1996, 2 pages.
- Maritz, Incentive, Jun. 1996, p. 111.
- Meridan Award Cards, JA8251.
- Allen et al., Overview of Smart Cards and the Industry, Smart Cards: Seizing Strategic Business Opportunities, Chapter 1, p. 2-20, Irwin Professional Publishing, 1997.
- Paper or Plastic? With these three incentives, The Choice if Yours, Incentive, Feb. 1996, 2 pages.
- Rossman, Kenneth, Summary Appraisal of Real Property.
- The Evolution of a New Consumerism, Chain Store Age, vol. 73, Jun. 1997, pp. 8-9.
- The Federal Transit Administration, TCRP Report 32 Multipurpose Transit Payment Media, Chapter 2 Multipurpose Fare Payment: Overview, p. 10-20.
- Nora Wood, The Power of the Card, Incentive, Jul. 1997, 6 pages.
- Welcome to Card Express CardEx, CardEx website archived by web.archive on Oct. 31, 1996, http://web.archive.org/web/*/http://www.cardex.com, retrieved Oct. 18, 2003, 7 pages.
- Welcome to Card Express, The CardEx Incentive Card, as disclosed in the CardEx web site archived by web.archive.org on Feb. 7, 1998, http://web.archive.org/web/*/http://www.cardex.com, retrieve Oct. 18, 2003, 8 pages.
- Wells Fargo Blazes New Trail for Homeowners.
- Kenneth Hein, What's the Deal?, Incentive, Jul. 1998, 7 pages.
Type: Grant
Filed: Jan 13, 2006
Date of Patent: May 10, 2011
Assignee: JPMorgan Chase Bank, N.A. (New York, NY)
Inventor: John Mark DeLoach (Wilmington, NC)
Primary Examiner: Mary Cheung
Assistant Examiner: Tien C Nguyen
Attorney: Hunton & Williams, LLP
Application Number: 11/331,141
International Classification: G06Q 40/00 (20060101);
