METHOD AND SYSTEM FOR A NO PRE-SET SPENDING LIMIT TRANSACTION CARD
TECHNICAL FIELD
The present subject matter relates generally to financial transaction processing systems of purchases made via a transaction card. More particularly, the present subject matter relates to a method and apparatus for processing user financial transactions made on a transaction card that combines features of a credit card and charge card for purchases of goods and/or services where the purchase amount equals or exceeds a user's communicated line of credit.
BACKGROUND The use of financial cards such as credit cards, charge cards, debits cards, and automated teller machine (ATM) cards is well known. These cards, which are used by consumers everyday, have many features and characteristics which offer flexibility to customers or users. For example, credit cards such as VISA®, MasterCard®, and Discover® credit cards typically offer revolving credit with a predetermined line of credit amount for each cardholder. Further, customers are able to carry a balance forward from billing cycle to billing cycle. The credit card customer will incur interest charges on the balance carried forward and must usually make a minimum payment. So long as a customer is carrying out transactions that together with their current credit card balance is less than their communicated line of credit, those transactions are typically approved. Once the customer's communicated line of credit is exceeded, a customer transaction on that credit card will typically be denied. The customer will generally have to make a payment to the credit card company sufficient to bring the credit card balance below the communicated line of credit or alternatively request a larger line of credit. The same issue will arise later if the line of credit is again exceeded.
Another type of financial card is a charge card such as cards issued by American Express. A charge card allows a customer to make purchases similar to a credit card. Unlike a credit card however, with a charge card, a customer is required to pay off the entire balance of the transactions or charges made on the charge card at the end of each billing cycle. Also, unlike a credit card, a charge card generally does not have a communicated line of credit associated with that card for that customer. A charge card with no preset or variable spending limit associated with the customer or charge card requires approval or authorization for each customer transaction on a transaction-by-transaction basis instead of on the basis of a fixed communicated line of credit amount. The customer spending limit is determined by authorization logic which evaluates the customer's credit at the time of the requested transaction and is typically based on a customer's spending and payment patterns, credit history, place of transaction, amount of transaction, and other parameters. The spending amounts authorized will vary from person to person depending on their particular financial characteristics including, among others, the user's payment and spending patterns and credit history. Further, different financial institutions generally have their own institution specific authorization or approval logic for their charge cards. However, the end result is typically the same, certain authorization logic is used to determine whether a transaction request will be approved or denied. The different features of financial transaction cards often result in the need for card user to obtain multiple transaction cards to meet their financial needs. Multiple transaction cards can be cumbersome, bulky and hard to keep track of. Thus, there is a need for a novel transaction card that advantageously combines the various features and functions of existing financial cards to more efficiently and conveniently provide for and meet a customers financial needs.
SUMMARY There is provided a process and system for a no pre-set spending limit transaction card with features and attributes of both a credit card and a charge card that can benefit both card users and card issuers. The novel method and apparatus uses a card with an overlimit spend feature and an associated communicated line of credit. The card user will be able to carry a balance like a credit card. And, when the user has reached or exceeded a communicated line of credit, each subsequent transaction request for a new transaction by the user is evaluated by the card issuer through an overlimit spend authorization logic or process on a transaction-by- transaction basis.
There is provided a computer-readable medium having computer-executable instructions for carrying out a financial transaction using a card having a corresponding card account with an associated line of credit and a card account balance. The computer-executable instructions enable performance of the steps of receiving an authorization request for a transaction amount to be charged against the card account, determining an aggregate amount of the card balance and transaction amount, comparing the aggregate amount against the line of credit. Further, if the aggregate amount is equal to or greater than the associated line of credit, executing authorization logic to determine an authorization response to the authorization request for said transaction amount. An authorization response is then generated. If the aggregate amount is less than the associated line of credit the authorization requested is approved. Additionally, the step of verifying that the card balance was paid down to the line of credit subsequent to the termination of a previous billing cycle may also be performed.
The is also provided a process for carrying out a financial transaction using a transaction card comprises the steps of having a transaction card account
corresponding to the transaction card with an associated line of credit and a transaction card balance of previously authorized transaction amounts in a current billing cycle, receiving an authorization request for a new transaction amount to be charged against the transaction card account for payment of goods or services, and determining an aggregate amount of the existing transaction card balance and the new transaction amount. The aggregate amount is then compared against the card's communicated line of credit, and when the aggregate amount is equal to or larger than the associated line of credit, overlimit spend authorization logic is executed to determine a response on whether the authorization request for the submitted transaction amount will approved or denied.
It is an object of the present subject matter to provide a method for providing an authorization response for a financial transaction request where a user has exceeded a communicated line of credit.
It is an object of the present subject matter to provide a method for providing an authorization response on a case-by-case basis for a financial transaction request by a user that has exceeded his/her communicated line of credit.
It is an object of the present subject matter to provide a method for providing an authorization response for a financial transaction where a user has presented a card where the card account balance has exceeded a communicated line of credit and where the card is a credit card, charge card, smart card, bank card, transaction card, access card, or an electronic commerce card.
Additional objects, advantages and novel features of the examples will be set forth in part in the description which follows, and in part will become apparent to those of ordinary skill in the art upon examination of the following and the accompanying drawings or may be learned by production or operation of the examples. The objects and advantages of the concepts may be realized and attained
by means of the methodologies, instrumentalities and combinations particularly pointed out in the appended claims.
BRIEF DESCRIPTION OF THE DRAWINGS
The drawing figures depict one or more implementations in accord with the present concepts, by way of example only, not by way of limitations. In the figures, like reference numerals refer to the same or similar elements. The description may be better understood when read in connection with the accompanying drawings, of which:
FIG. 1 depicts a block diagram generally showing a system that can be used to implement a no pre-set spending limit method; and
FIGs. 2 A and 2B illustrate steps that can be used to implement a no pre-set spending limit method.
DETAILED DESCRIPTION FIG. 1 illustrates an embodiment of a system 100 that can be used to implement the no pre-set spending limit or variable spend limit method in accordance with the present subject matter. In the embodiment shown, the system 100 comprises a user transaction card 10, a transaction card reader 20, and a transaction computer or processor 30 with access to a customer information database 35 and transaction card account 40.
A customer or transaction card user deciding to make a purchase of goods and/or services will present his transaction card 10 to the merchant providing the desired goods and services. The card or transaction card 10 presented could be a new type of card that can be used in the novel method described herein or could be any one of existing cards that have been adapted to be used in the embodiment of the novel method discussed herein. For example, the card 10 could be a typical credit card, charge card, smart card, bank card, transaction card, access card, or a type of
electronic commerce card. The merchant uses the card reader 20, or other device operable to read information from the transaction card 10. The card reader 20 reads information from the card 10 and communicates with an appropriate financial institution 50, e.g. a banking system or network associated with the institution 50 issuing the transaction card 10.
The card reader 20 is operatively coupled to the transaction computer or processor 30 of the financial institution 50. This may be done via a dedicated communication line or other means of two way communication between the card reader 20 and the transaction computer 30. The merchant's card reader 20 submits a transaction request for authorization or approval of the customer's desired purchase transaction. The transaction request submitted via the card reader 20 to the transaction computer or processor 30 may include, among other information, transaction card information, merchant identification, transaction amount, etc.
Those of skill in the art will readily recognize that although a card reader is shown as the device that communicates with the transaction processor, other devices may also be substituted. For example, a user may in some cases desire to retrieve cash from an automated teller machine (ATM). In that case, it would be the ATM machine that would communicate with the transaction processor 30. Other devices may be used that can operatively interact with the transaction processor 30, internet or web servers, interactive voice response units, graphical user interfaces, dual tone multi frequency generating devices, etc.
The financial institution 50 can comprise the transaction computer or processor 30, already mentioned, a transaction card account 40 associated with the particular transaction or user card 10, and a cardholder information database 35. The financial institution system 50 may also include a customer services component (not shown) that may operatively interact with a customer, merchant, or other institution
50 components, e.g., the transaction processor 30 or user information database 35, as necessary in a particular transaction request.
The transaction computer 30 may be operatively coupled to the merchant card reader 34, the user information database 35 and the transaction card account 40 associated with the transaction card 10. The transaction computer may manipulate and process information received or retrieved from these devices. The transaction computer 30 may be operatively coupled to the card reader 20 to received and respond to transaction request from a merchant. The transaction computer 30 may also be operatively coupled to the cardholder or customer information database 35 such that cardholder information, for example, customer address, credit history, spending patterns, payment patterns, or the like may be accessed and utilized as necessary to carryout authorization of merchant transaction requests.
Additionally, the transaction computer 30 may be operatively coupled to the transaction card account 40 in such a way that a transaction balance 43 corresponding to the transaction card account 40 may be accessed or updated as required. The transaction balance 43 is preferably an aggregate or sum of previously authorized transactions in a given billing cycle, e.g., in the present monthly billing cycle, for that transaction card 10 and any outstanding balance, e.g. purchases, finance charges, fees, etc., carried forward from previous billing cycles. The transaction computer 30 also has access to information relating to a communicated line of credit (LOC) amount 45 associated with a particular transaction card 10. The communicated line of credit is typically a fixed quantity and can be accessed by the transaction processor 30 in response to a transaction request. However, the communicated line of credit may be a quantity that is updated from time to time by the computer processor 30 as dictated by an institution's 50 guidelines.
In operation, a preferred embodiment of the transaction card 10 combines features of a charge card and a credit card in novel ways. In this embodiment, the transaction card 10 has an associated communicated line of credit similar to a credit card and a no pre-set or variable spending limit similar to a charge card. The communicated line of credit associated with the transaction card 10 allows a customer to carry a transaction card balance over time in an amount up to the communicated line of credit. Interest will be assessed on the customer's balance carried forward on a billing cycle basis, e.g., a monthly basis. The billing cycle can vary depending on the institution 50 and can be one month, 25 days or some other time period chosen by the institution. Once the line of credit limit associated with the transaction card 10 is reached or exceeded, each approval request for a new transaction above the communicated line of credit is preferably evaluated by the card issuer or institution issuer 50 on a transaction-by-transaction, or case-by-case, basis by a process that executes an overlimit spend authorization logic or process (shown in FIGs. 2A and 2B). The authorization process logic or process, executed by the logic transaction processor 30, evaluates the user's or customer's credit worthiness at the time of the requested transaction. The user's or customer's credit worthiness is based on various factors or parameters including, among others, current card balance, payment and spending patterns, credit history and ratings, customer's standing, etc. Those of skill in the art will readily appreciate that variable spend authorization logic or no pre-set spending limit algorithms are widely used and well known in the financial transaction card industry for responding to authorization of transaction requests. Different institutions 50 may have institution specific no pre-set spending limit authorization logic or algorithms that take into account a variety of customer parameters and assign varying importance to those parameters in making a determination of whether or not to authorize a submitted transaction request.
In an alternate embodiment, the user or customer may be required to pay down the revolving credit balance associated with the transaction card 10 down to the communicated line of credit limit before the Payment Due Date in order for new transaction amounts equaling or exceeding the communicated line of credit to be considered by the transaction processor for authorization (e.g., account in good standing). The transaction processor 30 can access the user information database 35 and/or the customer card account 40 to determine whether the user or customer has been paying the transaction card balance down each billing cycle.
The various processes and calculations carried out in the use of a no preset or variable spending limit card can be implemented on a computer or computers on computerized networks or systems, which may use on or more computer platforms. As is known to those of skill in the art, general purpose computers may be used to execute computer or machine readable instructions to carryout or perform desired steps or functions. A general-purpose computer typically comprises a central processor, an internal communication bus, various types of memory (RAM, ROM, EEPROM, cache memory, etc.), disk drives or other code and data storage systems, and one or more network interface cards or ports for communication purposes. A database, an associated web server application or other known applications and communications interfaces may be used as necessary to carryout desired steps or functions.
The computer or computerized machine can also comprise a data communication interface and may have a display and one or more user input devices, such as alphanumeric and other keys of a keyboard, a mouse, a trackball, etc. The display and user input devices together form a service-related user interface, for interactive control of the operation of a computer or computer system. These user interface elements may be locally coupled to the computer system, for example in a
workstation configuration, or the user interface elements may be remote from the computer and communicate therewith via a network.
Software functionalities involve programming, including executable code as well associated stored data. The software code is executable by the general-purpose computer. In operation, the executable program code and possibly associated data can be stored within the general-purpose computer platform. At other times, however, the software may be stored at other locations and/or transported for loading into the appropriate general-purpose computer system. Hence, the embodiments involve one or more software products in the form of one or more modules of code carried by at least one machine-readable medium. Execution of such code by a processor of the computer platform enables the platform to implement database and/or computer functions.
As used herein, terms such as computer or machine "readable medium" refer to any medium that participates in providing instructions to a processor for execution. Such a medium may take many forms, including but not limited to, non- volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as any of the storage devices in any computer(s) operating as one of the server platforms or client devices. Volatile media include dynamic memory, such as main memory of such a computer platform. Physical transmission media include coaxial cables, copper wire and fiber optics, including the wires that comprise a bus within a computer system. Carrier-wave transmission media can take the form of electric or electromagnetic signals, or acoustic or light waves such as those generated during radio frequency (RF) and infrared (E ) data communications. Common forms of computer-readable media therefore include, for example: a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch
cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave transporting data or instructions, cables or links transporting such a carrier wave, or any other medium from which a computer can read programming code and/or data. Many of these forms of computer readable media may be involved in carrying one or more sequences of one or more instructions to a processor for execution.
Referring now to FIGs. 2 A and 2B, a preferred embodiment is shown of the steps to carryout the no pre-set spending limit method 200 in accordance with the present subject matter. In steps 206 and 209, the cardholder or user presents the transaction card 10 to the merchant for the purchase of goods or services. The merchant then uses the card reader 20 to read the user account information on the user card 10 and to access the transaction computer 30 to obtain authorization or approval to carry out the point-of-sale transaction for the goods or services desired by the cardholder.
In step 212, the transaction computer 30, in communication with the card reader 20, receives the transaction card 10 information and a request for authorization or approval of a transaction amount for the service or goods desired.
In step 215, the transaction computer first makes a determination as to whether the card or transaction card presented has an "overlimit spend feature." In step 218, if the transaction card 10 does not have the "overlimit spend feature", then the transaction processor 30 carries out default authorization procedures specific for the credit card, charge card, or other presented card for approval or denial of the transaction amount. In step 221, the transaction computer 30 has determined that the transaction card 10 does have the "overlimit spend feature" and will access the appropriate
cardholder account 40 and user information database 35 as needed. In particular, the transaction computer 30 will access the communicated line of credit amount and the transaction balance of previously approved transactions associated with the transaction card 10 received. In step 224, the transaction computer 30 will aggregate or sum the transaction balance of previously approved transactions with the current or new transaction amount requested by the merchant.
In step 227, the transaction computer 30 will compare this aggregated figure to the communicated line of credit amount to determine whether the aggregated figure is equal to or larger than the communicated line of credit and whether the card account is in good standing.
In step 229, if the aggregated figure is not equal to or larger than the communicated line of credit and the account is in good standing, the transaction computer 30 will execute normal authorization procedures for the card presented, whether a credit card, charge card or other transaction card. In step 236, the transaction computer 30 will then notify the merchant that the merchant's transaction request has been authorized, hi step 239, the transaction computer 30 will update the cardholder's information, i.e., update the user information database 35 and the transaction balance 43, to reflect the approved transaction based on the aggregate figure being less than the communicated line of credit. The process 200 then proceeds back to step 206 in preparation for the next customer transaction.
Alternatively, in step 230, if the aggregated figure is equal to or larger than the communicated line of credit, then the transaction computer 30 will execute or carry out an overlimit spend authorization logic or algorithm to determine whether the merchant's transaction amount may nevertheless be approved. The approval or denial of the merchant's transaction amount is based on parameters related to the cardholder
and authorization logic or algorithm that is specific to the card issuer 50. For example, an institution 50 may use the cardholders credit history, past payment and spending patterns, amount of requested transaction, standing of member with the institution, risk level of transaction, etc., in their particular overlimit spend authorization logic or algorithm.
In step 233, the results of the authorization logic carried out by the transaction processor 30 are checked to determine whether the transaction has been approved or denied. If the transaction is approved based on the overlimit authorization logic, the merchant will be notified that the requested transaction request will be approved in Step 236. In step 239, the transaction computer 30 will then update the cardholder's information, i.e., update the user information database 35 and the transaction balance 43 to reflect the approved transaction amount based on the successful result or outcome of the overlimit authorization logic. The process 200 then proceeds back to step 206 in preparation for the next customer transaction. Alternatively, in step 233, if the transaction is denied based on the overlimit authorization logic or algorithm, the merchant will be notified that the requested transaction request will be denied in Step 241. In step 244, the transaction computer 30 will update the cardholder's information, i.e., update the user information database 35 and the transaction balance 43 to reflect the denied transaction amount based on the negative result of the overlimit authorization logic. The process 200 then proceeds back to step 206 in preparation for the next customer transaction.
Certain preferred aspects and embodiments of the novel subject matter have been described and illustrated by way of example only. Those skilled in that art will recognize that the preferred examples may be altered or amended without departing from the inventive spirit and scope of the subject matter. Therefore, the subject matter is not limited to the specific details, representative devices, and illustrated
examples in this description. The novel subject matter is limited only by the following claims and equivalents.