The present invention relates generally to credit cards/tokens and more particularly to a means of providing additional security to credit cards and transactions without changing underlying infrastructure.
Credit cards are ubiquitous with monetary transactions. They are used in a number of scenarios to purchase groceries, restaurant meals, retail/online products, gas, or just about anything. Most often a cash or check transaction can be replaced with a credit/debit card.
False charges create a tremendous burden on financial institutions and card holder alike. A lost or stolen card can easily be used by an unauthorized user to make purchases. Within several hours of obtaining a lost or stolen card, a thief can fraudulently charge thousands of dollars before a notification process can stop use of the card.
Some safeguard procedures have been put into place:
1. Retail clerk verifies customer signature matches that on the back of card.
2. Retail clerk verifies customer ID matches the name on card.
3. Authorization center uses sophisticated buying profiles to identify a potentially unauthorized purchase.
These safeguard procedures are not always performed at the point of sale, for example, a gas purchase. Many retail outlets do not require a signature for authentication with purchases under $50, nor does the retail clerk check the card carrier's ID.
There is accordingly an unmet need in the art to provide additional security to the use of credit cards while using the existing underlying infrastructure without changes.
An example of a prior art device is shown in U.S. Pat. No. 6,954,133, entitled Biometric smart card, biometric smart card reader, and method use issued Oct. 11, 2005, to Travis M. McGregor et al. McGregor claims an alternate means of exchanging data between authenticating bank and card to make transactions more secure.
Another example of a prior art device is shown in U.S. Pat. No. 4,667,087, entitled Secure Credit Card, issued May 19, 1987 to Max A. Quintana. Quintana teaches a means of obscuring critical account information until a user PIN is supplied.
It is the goal of the present invention to use the policies and equipment of existing infrastructure for credit card purchases. In addition, the present invention provides a means of managing internal account data of a credit card to prevent unauthorized use.
The present invention relates generally to credit cards/tokens and more particularly to a means of providing an additional layer of security to existing credit cards.
The apparatus and system according to the present invention provides a credit card with a display and integrated input mechanism that is electrically connected to a micro-controller equipped with internal memory. A user PIN is entered via the input mechanism and used to decrypt account data stored within the micro-controller's memory. The decrypted account data is then rendered on the integral display and sent to a transaction terminal when making a purchase.
Certain embodiments of the invention have other aspects in addition to or in place of those mentioned above. These aspects will become apparent to those skilled in the art from a reading of the following detailed description when taken with reference to the accompanying drawings.
Other objects and advantages of the present invention will be more readily apparent from the following detailed description when read in conjunction with the accompanying drawings.
The self-authenticating credit card 100 is shown schematically as being in two-way communication of account data 112 (in clear form) with a banking institution 111, and two-way communication of account data 112 (in clear form) with a transaction terminal 110. It will be understood that the terminal is exemplary, as is the banking institution shown, and it is contemplated that the present inventive self-authenticating credit card 100 would work with other types of suitable transaction terminals and with any banking institutions capable of accepting this type of credit card.
The micro-controller 102 includes a timer 103, encrypted account/reference data 104, clear reference data 105, and an encryption/decryption engine 106. The RF transponder 108 provides two-way communication of decrypted account data 112.
More specifically,
The micro-controller 102 is equipped with non-volatile memory used to store the encrypted account data 104. The account data 104 preferably includes of a number of different numeric elements describing a customer account.
For example, the encrypted account data 104 preferably includes the following:
The account data 104 is held in non-volatile memory in its encrypted form. Clear reference data 105 is stored in non-volatile memory, and is an arbitrary known string which is also included as account data when the encrypted account data 104 is created. That is, in addition to the aforementioned account data, the account data 104 also includes the identical arbitrary known string, all in encrypted form.
Since reference data 104 is present in both its cypher and clear forms, it is used to verify correct PIN entry. A PIN is entered via the input device 101 and received by the micro-controller 102. The entered PIN is used as an encryption key to decrypt account data 104 with the encryption/decryption engine 106, e.g. using an AES-128 (Advanced Encryption Standard). Other types of encryption can be employed as well, and all such variations are contemplated as being within the ambit of anyone skilled in the electronic encryption arts.
For example, specific account data 104 is encrypted using PIN=1234. If the user enters the correct PIN number (here, 1234), then the decrypted reference data contained within the account data 104 will match the clear reference data 105 permanently held in clear form. If the user enters 1233 (for instance), then no match will occur, and it will be presumed that an incorrect PIN was input.
Cryptographers generally do not believe doing a direct compare of an entered PIN with a PIN stored in memory is secure, inasmuch as a compromised memory will yield a means of accessing account data. That is, a skilled person might fraudulently access the memory, and thereby gain knowledge of the data in the memory. Therefore, it is desirable to make an indirect comparison, wherein knowledge of the data in the clear memory is useless since the encrypted memory will differ unless that data in the encrypted memory is first decrypted by entry of a correct PIN. This is as described in the preceding discussion.
The RF transponder 108 is provided for communication with the transaction terminal 110, as mentioned above. The micro-controller 102 will respond to requests to transmit account data 112 at any time. If the user has not input the correct PIN, garbled account data will be sent to the transaction terminal 110 resulting in a rejected purchase request. If, on the other hand, a correct PIN was entered, correct account data 112 will be sent to the transaction terminal 110.
A timer 103 is provided to limit the time account data 112 resides in memory in clear form. The timer 103 starts at the Lime a PIN is entered. Decrypted account data 112 residing in memory will get erased once the timer expires. A period for expiration is selected to provide adequate time to complete a transaction and short enough to prevent unauthorized access if the card is lost or stolen. This period of time can be selected, by way of an example, to be on the order of tens of seconds or even up to several minutes. Longer time periods, while possible, are inadvisable because of the risk of loss of the card.
The graphic display 109 allows rendering of a customer's picture ID once a correct PIN is entered. A digitized photograph taken at one's banking institution is coupled with the aforementioned exemplary account data which is also then encrypted with a default PIN to create the account data 104. Decryption of this account data 104, by use of the correct PIN, will restore the correct digital representation of a customer likeness which will be rendered on the graphic display 109. Furthermore, the present invention contemplates that digitized representation of the customer's signature can also be used in addition to customer photo for display by the graphic display 109, and such display can be together, or sequential, or in an alternating form. Other types of information can optionally also be provided, and all such variations are within the ambit of anyone having skill in the art of electronic displays.
An optional indicator 107 is provided to indicate correct or incorrect PIN entry. The correct PIN entry will result in the indicator lighting up and/or changing from one condition to another condition. If graphic content is rendered on graphic display 109, indicator 107 may not be necessary since a correct PIN will yield the correct customer likeness. If an incorrect PIN is used to decrypt account data 104, the image on the display 109 will appear as random dots (e.g. like “snow” on a TV) thereby providing visual feedback of correct or incorrect PIN entry.
When distributing the self-authenticating credit card 100, the dispensing bank will need to load the account data. The procedure is preferably performed via the RF transponder 108 that is used as a receiver. The account data in clear form is sent from the banking institution's computer 111 to the self-authenticating credit card 100 via the RF transponder 108. The account data is accompanied with a default PIN which the encryption/decryption engine 106 uses to encrypt received account data (that is, which is received in clear form) so as to encrypt that data so as to create account data 104 in a cypher form (that is, in encrypted form). Once the card 100 is distributed, it becomes possible for the customer to change their PIN in the manner shown and referenced in
In the locked state 202, the account data 104 is not accessible in clear form to the outside world until the user enters a correct PIN. A request from the transaction terminal 110 to transmit account information will cause the SACC 100 to transmit account data 112 which is in its zeroized state, and will therefore be rejected by the credit authorization facility; the transaction terminal 110 will therefore indicate an error.
In order to provide legitimate account data 112 to the transaction terminal 110, the SACC 100 must be unlocked by entering a correct PIN. Once the correct PIN is entered, the SACC 100 will transition to the unlocked state 203. If entry of the correct PIN fails a predetermined number of times, the SACC 100 will zeroize account data 104 and render itself inoperable. At this point, the SACC 100 must be returned to the banking institution for re-creation of valid account data 104.
The steps and operations discussed in the foregoing, and as further discussed below, are accomplished by programs and/or software stored in the micro-controller 102, and/or as part of the operating system of the micro-controller 102. These would be within the ambit of skill of anyone having skill in the programming arts for micro-controllers for smart credit cards.
Entry into the unlocked state 203 occurs when the correct user PIN has been entered via the input device 101. The PIN entry procedure and verification is shown in
In addition, once the unlocked state occurs, the user is able to define a new PIN. A four-digit PIN has a chance of 1/10000 of being guessed and is not considered cryptographically secure. Therefore, the user is encouraged to create a custom PIN with more digits/characters. Alpha characters, as well as numeric characters, are preferably supplied on the keys of the input device 101 allowing creation of PINs that are easier to remember.
Upon entry into the unlocked state 203, the timer 103 is started providing a means of limiting the time in which the SACC 100 remains in the unlocked state 203. Once the predetermined amount of time (as measured by the timer 103) expires, the account data in clear form 112 is zeroized and the SACC 100 reverts back to its locked state 202.
Assuming that the correct PIN is entered as determined at step 303, then the SACC 100 is in the unlocked state 203. In this unlocked state, the user can define a new PIN as shown in step 304. The new PIN will be used to encrypt the account data 112 together with the known reference data 105 to create new encrypted account data 104 as depicted in step 305.
If the decrypted reference data does not match the clear reference data 105 in step 303, a failed-attempts counter is incremented at step 306 and compared with a brute force attack limit (the brute force attack limit being a predetermined number of failed attempts) in step 307. If the failed attempts exceed the brute force attack limit at step 307, then all account parameters are zeroized as indicated in step 308, at which point the SACC 100 is no longer operable and requires reconfiguration by the issuing bank.
The foregoing embodiments are described in sufficient detail to enable those skilled in the art to make and use the invention, and it is to be understood that other embodiments would be evident based on the present disclosure and that process or mechanical changes may be made without departing from the scope of the present invention.
In the foregoing description, numerous specific details are given to provide a thorough understanding of the invention. However, it will be apparent that the invention may be practiced without these specific details. In order to avoid obscuring the present invention, some well-known circuits, system configurations, and process steps are not shown in detail and would be understood by anyone having skill in the relevant art.
The device 100 of the present invention can be powered by a self-contained battery (not shown), or can be externally powered by RF energy or microwave energy (not shown), or can draw power from a terminal which reads the device.
Likewise, the drawings showing embodiments of the apparatus/device are semi-diagrammatic and not to scale and, particularly, some of the dimensions are for clarity of presentation and may be shown greatly exaggerated in the drawings.
While the invention has been described in conjunction with a specific preferred embodiment which is considered to be the best mode, it is to be understood that many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the foregoing description and accompanying drawings. Accordingly, it is intended to embrace all such alternatives, modifications, and variations that fall within the scope of the included claims. All matters hithertofore set forth herein or shown in the accompanying drawings are to be interpreted in an illustrative and non-limiting sense.
This application is a Continuation of patent application Ser. No. 13/734,653, filed Jan. 4, 2013, which is a Continuation-in-Part of patent application Ser. No. 12/680,549, filed Mar. 26, 2010, which is a 372 national filing of international patent application PCT/US2008/077765, filed Sep. 26, 2008, which claims benefit of provisional patent application 60/975,356, filed Sep. 26, 2007, all of which are incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
3624938 | Richard | Dec 1971 | A |
4408119 | Decavele | Oct 1983 | A |
4614861 | Pavlov | Sep 1986 | A |
4879455 | Butterworth | Nov 1989 | A |
5623552 | Lane | Apr 1997 | A |
5799092 | Kristol | Aug 1998 | A |
5970143 | Schneier | Oct 1999 | A |
6257486 | Teicher et al. | Jul 2001 | B1 |
6954133 | McGregor | Oct 2005 | B2 |
7069447 | Corder | Jun 2006 | B1 |
8832440 | Johnson et al. | Sep 2014 | B2 |
9075571 | Bolotin et al. | Jul 2015 | B2 |
9262611 | Johnson et al. | Feb 2016 | B2 |
10223856 | Johnson et al. | Mar 2019 | B2 |
10614462 | Johnson | Apr 2020 | B2 |
20010034717 | Whitworth | Oct 2001 | A1 |
20020153424 | Li | Oct 2002 | A1 |
20020180584 | McGregor | Dec 2002 | A1 |
20030007561 | Ong | Apr 2003 | A1 |
20030085286 | Kelley | May 2003 | A1 |
20030177347 | Schneier | Sep 2003 | A1 |
20050086471 | Spencer | Apr 2005 | A1 |
20050240528 | Hendrick | Oct 2005 | A1 |
20060213972 | Kelley | Sep 2006 | A1 |
20070145121 | Dallal | Jun 2007 | A1 |
20070214093 | Colella | Sep 2007 | A1 |
20080029607 | Mullen | Feb 2008 | A1 |
20090108064 | Fernandes | Apr 2009 | A1 |
20090309701 | Peled | Dec 2009 | A1 |
20100230487 | Johnson et al. | Sep 2010 | A1 |
20140195441 | Johnson | Jul 2014 | A1 |
20160119339 | Bolotin et al. | Apr 2016 | A1 |
20160259736 | Bolotin et al. | Sep 2016 | A1 |
Number | Date | Country |
---|---|---|
1020020045187 | Jun 2002 | KR |
102003033888 | May 2003 | KR |
200915235 | Apr 2009 | TW |
WO-1988009019 | Nov 1988 | WO |
WO-2001061640 | Aug 2001 | WO |
WO-2007057603 | May 2007 | WO |
WO-2009042819 | Apr 2009 | WO |
Entry |
---|
Chip-and-PIN vs. Chip-and-Signature (Year: 2012). |
Self AuthenticatingCreditCard Rocks Keyboard and Display (Year: 2007). |
“U.S. Appl. No. 12/680,549, Advisory Action dated Apr. 19, 2016”, 3 pgs. |
“U.S. Appl. No. 12/680,549, Advisory Action dated Nov. 16, 2012”, 3 pgs. |
“U.S. Appl. No. 12/680,549, Final Office Action dated Feb. 10, 2016”, 8 pgs. |
“U.S. Appl. No. 12/680,549, Final Office Action dated Sep. 6, 2012”, 8 pgs. |
“U.S. Appl. No. 12/680,549, Final Office Action dated Oct. 12, 2017”, 8 pgs. |
“U.S. Appl. No. 12/680,549, Final Office Action dated Oct. 17, 2011”, 7 pgs. |
“U.S. Appl. No. 12/680,549, Final Office Action dated Nov. 22, 2016”, 8 pgs. |
“U.S. Appl. No. 12/680,549, Non Final Office Action dated Apr. 1, 2011”, 7 pgs. |
“U.S. Appl. No. 12/680,549, Non Final Office Action dated May 23, 2012”, 7 pgs. |
“U.S. Appl. No. 12/680,549, Non Final Office Action dated Jun. 6, 2018”, 8 pgs. |
“U.S. Appl. No. 12/680,549, Non Final Office Action dated Jul. 11, 2017”, 8 pgs. |
“U.S. Appl. No. 12/680,549, Non Final Office Action dated Jul. 29, 2016”, 8 pgs. |
“U.S. Appl. No. 12/680,549, Non Final Office Action dated Oct. 26, 2015”, 9 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Jan. 10, 2018 to Final Office Action dated Oct. 12, 2017”, 9 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Jan. 17, 2012 to Final Office Action dated Oct. 17, 2011”, 4 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Jan. 25, 2016 to Non Final Office Action dated Oct. 26, 2015”, 8 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Apr. 5, 2017 to Final Office Action dated Nov. 22, 2016”, 11 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Apr. 12, 2016 to Final Office Action dated Feb. 10, 2016”, 11 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Jul. 15, 2011 to Non Final Office Action dated Apr. 1, 2011”, 10 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Aug. 23, 2012 to Non Final Office Action dated May 23, 2012”, 11 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Sep. 27, 2017 to Non Final Office Action dated Jul. 11, 2017”, 11 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Oct. 28, 2016 to Non Final Office Action dated Jul. 29, 2016”, 10 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Nov. 9, 2012 to Final Office Action dated Sep. 6, 2012”, 10 pgs. |
“U.S. Appl. No. 13/734,653, Advisory Action dated Mar. 13, 2019”, 3 pgs. |
“U.S. Appl. No. 13/734,653, Advisory Action dated Jul. 15, 2016”, 3 pgs. |
“U.S. Appl. No. 13/734,653, Appeal Brief filed Jul. 31, 2019”, 24 pgs. |
“U.S. Appl. No. 13/734,653, Examiner Interview Summary dated Feb. 8, 2019”, 3 pgs. |
“U.S. Appl. No. 13/734,653, Examiner Interview Summary dated Jun. 25, 2018”, 3 pgs. |
“U.S. Appl. No. 13/734,653, Final Office Action dated Apr. 13, 2016”, 18 pgs. |
“U.S. Appl. No. 13/734,653, Final Office Action dated Sep. 21, 2017”, 29 pgs. |
“U.S. Appl. No. 13/734,653, Final Office Action dated Dec. 11, 2018”, 20 pgs. |
“U.S. Appl. No. 13/734,653, Non Final Office Action dated Feb. 9, 2018”, 29 pgs. |
“U.S. Appl. No. 13/734,653, Non Final Office Action dated Feb. 10, 2017”, 26 pgs. |
“U.S. Appl. No. 13/734,653, Non Final Office Action dated Aug. 20, 2015”, 16 pgs. |
“U.S. Appl. No. 13/734,653, Notice of Allowance dated Nov. 27, 2019”, 22 pgs. |
“U.S. Appl. No. 13/734,653, Response filed Feb. 5, 2019 to Final Office Action dated Dec. 11, 2018”, 13 pgs. |
“U.S. Appl. No. 13/734,653, Response filed May 10, 2017 to Non Final Office Action dated Feb. 10, 2017”, 15 pgs. |
“U.S. Appl. No. 13/734,653, Response filed Jun. 13, 2016 to Final Office Action dated Apr. 13, 2016”, 8 pgs. |
“U.S. Appl. No. 13/734,653, Response filed Jul. 5, 2018 to Non Final Office Action dated Feb. 9, 2018”, 21 pgs. |
“U.S. Appl. No. 13/734,653, Response filed Nov. 19, 2015 to Non Final Office Action dated Aug. 20, 2015”, 16 pgs. |
“U.S. Appl. No. 13/734,653, Response filed Dec. 21, 2017 to Final Office Action dated Sep. 21, 2017”, 21 pgs. |
“International Application Serial No. PCT/US2008/077765, International Preliminary Report on Patentability dated Mar. 30, 2010”, 5 pgs. |
“International Application Serial No. PCT/US2008/077765, International Search Report dated Mar. 31, 2009”, 2 pgs. |
“International Application Serial No. PCT/US2008/077765, Written Opinion dated Mar. 31, 2009”, 4 pgs. |
“U.S. Appl. No. 12/680,549, Examiner Interview Summary dated Sep. 5, 2018”, 3 pgs. |
“U.S. Appl. No. 12/680,549, Notice of Allowability dated Nov. 28, 2018”, 4 pgs. |
“U.S. Appl. No. 12/680,549, Notice of Allowance dated Oct. 23, 2018”, 8 pgs. |
“U.S. Appl. No. 12/680,549, Response filed Aug. 30, 2018 to Non Final Office Action dated Jun. 6, 2018”, 15 pgs. |
Number | Date | Country | |
---|---|---|---|
20200211014 A1 | Jul 2020 | US |
Number | Date | Country | |
---|---|---|---|
60975356 | Sep 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13734653 | Jan 2013 | US |
Child | 16805148 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12680549 | US | |
Child | 13734653 | US |