Source: https://patents.google.com/patent/US8380628B1/en
Timestamp: 2019-12-14 13:42:58
Document Index: 174012959

Matched Legal Cases: ['Application No. 2001273490', 'Application No. 2001273490', 'Application No. 2001273490', 'Application No. 2005271884', 'Application No. 2005271884', 'Application No. 2008202099', 'Application No. 2008202099', 'Application No. 2', 'Application No. 01812985', 'Application No. 01812985', 'Application No. 200580030587', 'Application No. 200580030587', 'Application No. 201010239623', 'Application No. 201010239623', 'Application No. 01', 'Application No. 01', 'Application No. 01', 'Application No. 05', 'Application No. 180640', 'Application No. 379', 'Application No. 2002', 'Application No. 2002', 'Application No. 2007', 'Application No. 2007', 'Application No. 7002939', 'Application No. 7017899', 'Application No. 7017899', 'Application No. 523746', 'Application No. 523746', 'Application No. 552703', 'Application No. 552703', 'Application No. 552703', 'Application No. 552703']

US8380628B1 - System and method for verifying commercial transactions - Google Patents
System and method for verifying commercial transactions Download PDF
US8380628B1
US8380628B1 US09/617,361 US61736100A US8380628B1 US 8380628 B1 US8380628 B1 US 8380628B1 US 61736100 A US61736100 A US 61736100A US 8380628 B1 US8380628 B1 US 8380628B1
US09/617,361
2000-07-17 Application filed by Harris Intellectual Property LP filed Critical Harris Intellectual Property LP
2000-07-17 Priority to US09/617,361 priority Critical patent/US8380628B1/en
2001-07-16 Priority claimed from PCT/US2001/022313 external-priority patent/WO2002008995A1/en
2009-06-01 Assigned to HARRIS INTELLECTUAL PROPERTY, LP reassignment HARRIS INTELLECTUAL PROPERTY, LP ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HARRIS, DAVID N.
2013-02-19 Publication of US8380628B1 publication Critical patent/US8380628B1/en
239000011269 tar Substances 0 description 22
A system and method is disclosed for verifying a commercial transaction between a card-holder, a merchant, and a credit card company. The card-holder makes a purchase with the merchant using a full credit card number. The merchant submits a transaction approval request for approval with the credit card company. The credit card company executes conventional credit approval of the transaction approval request, as well as verifies the transaction approval request with the card-holder. An approval is sent to the merchant only after the transaction approval request is both conventionally approved by the credit card company and verified by the card-holder. The card-holder, or the credit card company, may initiate verification of the transaction approval request.
In a particular embodiment, the authorization module, responsive to instructions from the account holder, can selectively disable the verification process by automatically verifying subsequent transaction approval requests without further input from the account holder.
The present invention is descried with reference to the following drawings, wherein like reference numbers denote substantially similar elements.
FIG. 9 is a flowchart summarizing one method of performing the fifth step (card-holder verification) of the method of FIG. 7; and
FIG. 4 shows an example of a credit approval request data structure 400 suitable for use with a particular embodiment of the present invention. Those skilled in the art will recognize data structure 400 as a linked-list of records 402(1−n). Each of records 402(1−n) represents a pending TAR and includes a full credit card number 404, a purchase description 406, a purchase price 408, merchant information 410, purchase date and time information 412, a verified flag 414, a verification initiated flag 415, an approved flag 416, a denied flag 418, and a pointer 420. Full credit card number 404, purchase description 406, purchase price 408, merchant information 410, and purchase date and time information 412 are received by server 200 from merchant 104 with the TAR. Verified flag 414, approved flag 416, and denied flag 418 are used to indicate the status of each record 402 in the authorization process, as will be explained in greater detail below. Pointer 420 indicates the memory address of the next record 402(+1) in the list. The last record 402(n) includes an end of list value 422, that indicates that record 402(n) is the last record in the list.
FIG. 5 shows an example of a card-holder data structure 500 suitable for storing card-holder data in card-holder list module 222. Those skilled in the art will recognize that data structure 500 is a linked list of records 502(1−n), with one record 502 for each valid credit account extended by credit card company 106. Each record 502 includes a full credit card number 504 issued to an associated card-holder, a personal identification number (PIN) 506, card-holder information 508, contact information 510, a credit limit 512, a verification requested flag 514, an initiate verification flag 516, and a pointer 518.
FIG. 6 shows an example of a purchase history data structure 606, suitable for use with a particular embodiment of the present invention. Purchase history data structure 600 is a linked-list of records 602(1−n), each of which includes a full credit card number 604, purchase information 606, a purchase price 608, merchant information 610, a verification date and time 612, and a pointer 614. Credit card number 604 identifies the particular transaction with the associated card-holder. Purchase information 606 includes information (e.g., product description) that will help identify the transaction to the card-holder. Purchase price 608 indicates the cost associated with the purchase. Merchant information 610 identifies the merchant that submitted the TAR. Verification date and time 612 indicates when, if at all, the associated card-holder verified the TAR. Pointer 614 indicates the address of the next record 602 in data structure 600. End of list indicator 616(n) indicates that record 602(n) is the last record in purchase history data structure 600.
In an alternate embodiment, system 200 can be modified to allow account-holder 102 to preapprove certain charges. For example, card-holder list 222 could include a field for preapproved merchants (or any other desirable criteria). Then, when a transaction approval request is processed, authorization module 226 can compare the merchant identification to the associated card-holder's preapproved merchant's list, and, if the merchant appears on the list, automatically verify the TAR. Card-holder 102 could access system 200 to modify such preapproved lists via internetwork 110, network 114, or any other means known for updating customer data.
In the particular embodiment of the present invention shown in FIGS. 1-3, interactive verification module 306 communicates with card-holders 102 via card-holder communications module 224 and network interface 204 and telecommunications device 214. Card-holder communications module 224 periodically polls network interface 204 and telecommunications device 214 for incoming connection requests (e.g., e-mail, network connection, phone call, etc.) and establishes any such connections. Such communications programs (e.g., e-mail software, network protocols, etc) are well known to those skilled in the art, and are not therefore described in detail so as not to unnecessarily obscure the present invention.
There are many possible ways to present pending TARs to card-holder 102(x) and to receive verification instructions from card-holder 102(x), depending on the type of connection established with server 200. For example, if card-holder 102 establishes an HTTP connection with server 200, then pending TARs could be presented in the form of an interne web page. Alternatively, if the connection between card-holder 102(x) and server 200 is a telephone voice connection, then pending TARs can be presented to card-holder 102(x) via an automated text to speech system, such as are well known in the art. Card-holder 102(x) could then transmit verification instructions via voice or keypad commands (e.g. touching button 1 to verify, or touching button 2 to disclaim). As yet another example, in the case where the connection request is in the form of an e-mail response, the e-mail response can include verification instructions (e.g., in the subject line of the e-mail) that can be automatically processed by interactive verification module 306. While using any of the above-described types of connections to verify TARs is considered to be a novel aspect of the present invention, no particular type of connection is considered to be an essential element of the present invention.
The description of particular embodiments of the present invention is now complete. Many of the described features may be substituted, altered or omitted without departing from the scope of the invention. For example, the present invention may be implemented in conjunction with alternate types of accounts (e.g. debit accounts) requiring secure processing in addition to the credit card type account described herein. As another example, a third party verification company 108 may employ the transaction processing methods described herein on behalf of credit card company 106, and then transmit indicia of verification to credit card company 106. These and other deviations from the particular embodiments shown will be apparent to those skilled in the art, particularly in view of the foregoing disclosure.
1. In a computer system, a method for verifying a commercial transaction between a user with credit card data and a merchant, said method comprising:
receiving instructions from an account-holder associated with said credit card data to selectively disable a previously enabled verification function;
transmitting an approval to said merchant without verifying said transaction approval request with said account-holder responsive to the selectively disabled verification function;
receiving instructions from said account-holder to selectively enable said verification function;
receiving a subsequent transaction approval request from another merchant;
electronically verifying said subsequent transaction approval request with said account-holder, responsive to the selectively enabled verification function, via a communication with said account-holder separate from said communication with said another merchant; and
transmitting an approval to said another merchant only if said subsequent transaction approval request is verified by said account-holder or if said verification function has again been disabled.
2. A method according to claim 1, wherein said step of verifying said subsequent transaction approval request with said account-holder includes prompting said account-holder to verify said transaction approval request.
3. A method according to claim 2, wherein said step of prompting said account-holder includes sending an electronic message to said account-holder.
4. A method according to claim 3, wherein said step of verifying said subsequent transaction approval request with said account-holder includes receiving a reply to said electronic message.
5. A method according to claim 2, wherein said step of prompting said account-holder includes placing an automated telephone call to said account-holder.
6. A method according to claim 5, wherein said step of placing an automated telephone call to said account-holder includes:
establishing a telephone connection with said account-holder;
reciting at least a portion of said subsequent transaction approval request to said account holder; and
receiving verification instructions from said account-holder with respect to said subsequent transaction approval request.
7. A method according to claim 6, wherein said step of placing an automated telephone call to said account-holder further includes receiving an authentication code from said account-holder prior to said step of reciting at least a portion of said subsequent transaction approval request to said account holder.
8. A method according to claim 1, wherein said step of electronically verifying said subsequent transaction approval request with said account-holder includes disabling any notification to said account-holder and waiting for said account-holder to initiate communication with said computer system.
9. A method according to claim 8, wherein said communication with said computer system is initiated by said account-holder via a network connection.
10. A method according to claim 8, wherein said step of electronically verifying said subsequent transaction approval request with said account-holder includes:
receiving a connection request from said account-holder via a network;
establishing a network connection with said account-holder;
authenticating said account-holder;
transmitting at least a portion of said subsequent transaction approval request to said account-holder; and
11. A method according to claim 8, wherein said communication with said computer system is initiated by said account-holder via a telephone connection.
12. A method according to claim 8, wherein said step of electronically verifying said subsequent transaction approval request with said account-holder includes:
receiving a telephone call from said account-holder;
reciting at least a portion of said subsequent transaction approval request to said account-holder; and
receiving verification instructions from said account-holder with respect to said transaction approval request.
13. A method according to claim 1, wherein said step of electronically verifying said subsequent transaction approval request with said account-holder includes automatically disclaiming said approval request if said subsequent transaction approval request is not verified by said account-holder within a predetermined time interval.
14. A method according to claim 13, further comprising transmitting notice to said account-holder when said subsequent transaction approval request is disclaimed.
15. A method according to claim 1, wherein said step of electronically verifying said subsequent transaction approval request with said account-holder includes:
transmitting a verification request identifying said subsequent transaction approval request to a third-party for verification of said subsequent transaction approval request with said account-holder; and
receiving indicia of verification from said third-party indicating whether said account-holder verified said subsequent transaction approval request.
16. A computer system for verifying a commercial transaction between a user with credit card data and a merchant, said computer system comprising:
a processing unit for processing data and code;
memory for storing said data and said code, said code including
an account-holder communications module operative to facilitate a separate connection with an account-holder associated with said credit card data for said account-holder to verify said transaction approval request, and
an authorization module responsive to receipt of said transaction approval request and operative to transmit an approval to said merchant if said transaction approval request is verified, said authorization module being configurable to cooperate with said account-holder communication module for obtaining account-holder verification of said transaction approval request or to automatically verify said transaction approval request without obtaining verification from said account-holder, said authorization module including an interactive verification module operative to wait for said account-holder to initiate said connection with said account-holder communication module, any prior notification to said account-holder regarding said transaction being disabled.
17. In a computer system, a method for verifying a commercial transaction between a user with credit card data and a merchant, said method comprising:
electronically verifying said transaction approval request with an account-holder associated with said credit card data via a communication with said account-holder separate from said communication with said merchant, said electronic verification including disabling any notification to said account-holder and waiting for said account-holder to initiate communication with said computer system;
enabling the account-holder to disable the step of electronically verifying;
automatically verifying the transaction approval request, if the account-holder has disabled the step of electronically verifying; and
transmitting an approval to said merchant if said transaction approval request is verified.
18. A computer-readable medium having code embodied therein for causing an electronic device to perform the method of claim 17.
US09/617,361 2000-07-17 2000-07-17 System and method for verifying commercial transactions Active 2025-01-07 US8380628B1 (en)
US09/617,361 US8380628B1 (en) 2000-07-17 2000-07-17 System and method for verifying commercial transactions
US09/760,271 US8352369B2 (en) 2000-07-17 2001-01-12 System and method for pre-verifying commercial transactions
PCT/US2001/022313 WO2002008995A1 (en) 2000-07-17 2001-07-16 System and method for verifying commercial transactions
CA 2415366 CA2415366A1 (en) 2000-07-17 2001-07-16 System and method for verifying commercial transactions
CN 01812985 CN1203437C (en) 2000-07-17 2001-07-16 System and method for verifying commercial transactions
JP2002514625A JP2004519022A (en) 2000-07-17 2001-07-16 System and method for confirming the quotient settlement
NZ52374601A NZ523746A (en) 2000-07-17 2001-07-16 System and method for verifying commercial transactions
KR20027017899A KR100853868B1 (en) 2000-07-17 2001-07-16 System and method for verifying commercial transactions
EP01952770A EP1312009A4 (en) 2000-07-17 2001-07-16 System and method for verifying commercial transactions
AU7349001A AU7349001A (en) 2000-07-17 2001-07-16 System and method for verifying commercial transactions
AU2008202099A AU2008202099A1 (en) 2000-07-17 2008-05-09 System and method for verifying commercial transactions
AU2010219317A AU2010219317A1 (en) 2000-07-17 2010-09-07 System and method for verifying commercial transactions
US09/760,271 Continuation-In-Part US8352369B2 (en) 2000-07-17 2001-01-12 System and method for pre-verifying commercial transactions
US8380628B1 true US8380628B1 (en) 2013-02-19
ID=24473350
US09/617,361 Active 2025-01-07 US8380628B1 (en) 2000-07-17 2000-07-17 System and method for verifying commercial transactions
US09/760,271 Active 2025-05-22 US8352369B2 (en) 2000-07-17 2001-01-12 System and method for pre-verifying commercial transactions
US (2) US8380628B1 (en)
KR (1) KR100853868B1 (en)
AU (1) AU2010219317A1 (en)
US20170344991A1 (en) * 2014-11-10 2017-11-30 Shlomo MARK User controlled remote credit and bank card transaction verification system
US5104149A (en) 1989-10-20 1992-04-14 Gao Gesellschaft Fur Automation Und Organisation Mbh Identity card and a method for producing an identity card
JPH11250193A (en) 1998-03-04 1999-09-17 Oki Electric Ind Co Ltd Ic card and its transaction processing method
KR20000037355A (en) 2000-04-19 2000-07-05 김진호 Method for approving electronic commerce using the short message service and system therefor
WO2001061640A1 (en) 2000-02-16 2001-08-23 Ong Yong Kin Michael Electronic credit card - ecc
JP2001283118A (en) 2000-03-30 2001-10-12 Internatl Business Mach Corp <Ibm> On-line settling system and settling method in on-line shopping and server and seller's terminal
JP2001351050A (en) 2000-06-05 2001-12-21 Shigeru Nakatsuru Card loss/robbery notification processing system for quickly notifying loss/robbery of card such as cash card, credit card and debit card, recording medium with recorded notification processing program and notification processing method
US20020143570A1 (en) 2001-03-30 2002-10-03 Fujitsu Limited Credit card management method, credit card management program, credit card management device
JP2002324219A (en) 2001-04-24 2002-11-08 Seiko Instruments Inc Card authentication system
KR20040072447A (en) 2003-02-12 2004-08-18 정은영 Finance security system using a mobile telephone device applying an account and payment limit money and method of the same
US20060261152A1 (en) 2004-01-20 2006-11-23 Kamfu Wong Banking computer account system with lock for secure payment via telephone
WO2010105627A2 (en) 2009-03-17 2010-09-23 Arkitema K/S Composite sandwich panel
2000-07-17 US US09/617,361 patent/US8380628B1/en active Active
2001-01-12 US US09/760,271 patent/US8352369B2/en active Active
2001-07-16 KR KR20027017899A patent/KR100853868B1/en not_active IP Right Cessation
2010-09-07 AU AU2010219317A patent/AU2010219317A1/en not_active Abandoned
CN1418351A (en) 2000-02-16 2003-05-14 王永坚（迈克尔） Electronic credit card-ECC
JP2002298045A (en) 2001-03-30 2002-10-11 Fujitsu Ltd Credit card control method
AU Application No. 2001273490, Office Action dated Aug. 10, 2006.
AU Application No. 2001273490, Office Action dated Jul. 19, 2007.
AU Application No. 2001273490, Office Action dated May 7, 2008.
AU Application No. 2005271884, Notice of Allowance dated Mar. 9, 2011.
AU Application No. 2005271884, Office Action dated Apr. 9, 2010.
AU Application No. 2008202099, Office Action dated Dec. 10, 2009.
AU Application No. 2008202099, Office Action dated Dec. 9, 2008.
Boards of Appeal of the European Patent Office / Datasheet for the Decision of Dec. 13, 2006 regarding: Case No. T 1227/05-3.5.01 (EP App. No. 01964907.8).
CA Application No. 2,415,366, Office Action dated Jan. 11, 2012.
CN Application No. 01812985.4, Notice of Allowance dated Jan. 14, 2005 (English translation).
CN Application No. 01812985.4, Office Action dated May 28, 2004 (English translation).
CN Application No. 200580030587.X, Office Action dated Feb. 12, 2010 (English translation).
CN Application No. 200580030587.X, Office Action dated Jul. 7, 2011 (English translation).
CN Application No. 201010239623.6, Office Action dated Jun. 1, 2012 (English translation).
CN Application No. 201010239623.6, Office Action dated May 17, 2011 (English translation).
Dialog reference, file 9 #0019808924 Certificate Manager v3.0 the most Flexible Approach to digital Certificate and Smart Card Production to Date; Increased Interoperability Provides a cost effective and Mnageable Solution for High-volume Production. *
EP Application No. 01 952 770.04-2221, European Search Report dated Jun. 25, 2007.
EP Application No. 01 952 770.04-2221, Office Action dated Apr. 24, 2008.
EP Application No. 01 952 770.04-2221, Office Action dated Sep. 13, 2007.
EP Application No. 05 769 377.2, Office Action dated Jul. 10, 2010.
IL Application No. 180640, Office Action dated Jan. 31, 2010 (English translation).
IN Application No. 379/DELNP/2007, Office Action dated Mar. 7, 2011 (English translation).
Introduction of Credit Card that a User Can Set Up a Use Environment, Pack, Jong Min, Naver News, Oct. 30, 2003.
JP Application No. 2002-514625, Office Action dated May 16, 2011 (English translation).
JP Application No. 2002-514625, Office Action dated Nov. 16, 2011 (English translation).
JP Application No. 2007-521513, Office Action dated Feb. 1, 2012 (English translation).
JP Application No. 2007-521513, Office Action dated Jul. 6, 2011 (English translation).
KR Application No. 7002939/2007, Office Action dated Oct. 17, 2011 (English translation).
KR Application No. 7017899/2002, Notice of Allowance dated May 30, 2008 (English translation).
KR Application No. 7017899/2002, Office Action dated Aug. 24, 2007 (English translation).
MX Application No. MX/A/2007/000484, Notice of Allowance dated May 24, 2010 (English translation).
MX Application No. MX/A/2007/000484, Office Action dated Dec. 15, 2009 (English translation).
MX Application No. MX/A/2007/000484, Office Action dated Jun. 3, 2009 (English translation).
NZ Application No. 523746, Notice of Allowance dated Oct. 12, 2004.
NZ Application No. 523746, Office Action dated Jan. 29, 2004.
NZ Application No. 552703, Notice of Allowance dated Mar. 10, 2010.
NZ Application No. 552703, Office Action dated Aug. 11, 2008.
NZ Application No. 552703, Office Action dated Aug. 18, 2009.
NZ Application No. 552703, Office Action dated Nov. 19, 2009.
PCT Application No. PCT/US2001/022313, International Preliminary Report on Patentability dated Dec. 15, 2003.
PCT Application No. PCT/US2001/022313, International Search Report dated Oct. 9, 2001.
PCT Application No. PCT/US2001/022313, Written Opinion dated Jul. 24, 2003.
PCT Application No. PCT/US2005/024242, International Preliminary Report on Patentability dated Apr. 12, 2007.
PCT Application No. PCT/US2005/024242, International Search Report and Written Opinion dated Feb. 12, 2007.
U.S. Appl. No. 09/760,271, Advisory Action dated Jul. 5, 2005.
U.S. Appl. No. 09/760,271, Examiner's Answer to Appeal Brief dated Aug. 6, 2009.
U.S. Appl. No. 09/760,271, Examiner's Answer to Appeal Brief dated Mar. 26, 2008.
U.S. Appl. No. 09/760,271, Granted Appeal Brief Notice dated Nov. 19, 2009.
U.S. Appl. No. 09/760,271, Notice of Abandonment dated Sep. 8, 2011.
U.S. Appl. No. 09/760,271, Notice of Appeal Brief Rejection dated Nov. 21, 2007.
U.S. Appl. No. 09/760,271, Notice of Granted Petition to Revive Application dated Nov. 23, 2011.
U.S. Appl. No. 09/760,271, Notice of Reply Brief Accepted dated Jul. 24, 2008.
U.S. Appl. No. 09/760,271, Office Action dated Jan. 10, 2012.
U.S. Appl. No. 09/760,271, Office Communication dated Jun. 29, 2011.
U.S. Appl. No. 09/760,271, PTO Decision dated Jun. 29, 2009.
U.S. Appl. No. 10/889,227, Notice of Allowance dated Jun. 15, 2007.
U.S. Appl. No. 10/889,227, Office Action dated Jan. 19, 2007.
U.S. Appl. No. 10/889,227, Restriction Requirement dated Sep. 19, 2006.
U.S. Appl. No. 11/895,837, Notice of Allowance dated Jan. 11, 2010.
U.S. Appl. No. 11/895,837, Office Action dated Jun. 12, 2008.
U.S. Appl. No. 11/895,837, Office Action dated Mar. 9, 2009.
U.S. Appl. No. 11/895,837, Office Communication dated Jun. 9, 2010.
U.S. Appl. No. 12/803,219, Notice of Allowance dated Aug. 8, 2011.
U.S. Appl. No. 12/803,219, Office Action dated Aug. 31, 2010.
U.S. Appl. No. 12/803,219, Office Action dated May 9, 2011.
U.S. Appl. No. 13/300,142, Office Action dated Apr. 2, 2012.
KR20040007220A (en) 2004-01-24
AU2010219317A1 (en) 2010-09-30
US20020007345A1 (en) 2002-01-17
KR100853868B1 (en) 2008-08-22
US8352369B2 (en) 2013-01-08
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HARRIS, DAVID N.;REEL/FRAME:022761/0897