Source: https://patents.google.com/patent/US20080155655A1/en
Timestamp: 2018-04-22 08:28:20
Document Index: 398933976

Matched Legal Cases: ['Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60']

US20080155655A1 - System and method for secure telephone and computer transactions using voice authentication - Google Patents
US20080155655A1
US20080155655A1 US12044304 US4430408A US2008155655A1 US 20080155655 A1 US20080155655 A1 US 20080155655A1 US 12044304 US12044304 US 12044304 US 4430408 A US4430408 A US 4430408A US 2008155655 A1 US2008155655 A1 US 2008155655A1
US12044304
US8555358B2 (en )
This application is a continuation of U.S. application Ser. No. 10/764,099 filed Jan. 23, 2004, which claims priority to U.S. Provisional Patent Application No. 60/442,143, filed on Jan. 23, 2003 All of the aforementioned applications are incorporated by reference in their entireties herein.
Additional detail regarding completion of the transaction using MasterCard®'s implementation of the 3-D Secure protocol can be found in the following applications, all of which are also incorporated herein by reference in their entirety: U.S. patent application Ser. No. 09/963,274, entitled “A Universal and Interoperable System and Method Utilizing a Universal Cardholder Authentication Field (UCAF) For Authentication Data Collection and Validation,” filed on Sep. 26, 2001; U.S. Provisional Patent Application No. 60/280,776, entitled “System and Method for Secure Payment Application (SPA) and Universal Cardholder Authentication,” filed on Apr. 2, 2001; U.S. Provisional Patent Application No. 60/295,630, entitled “Method and Process for a Secure Payment Application Using a Universal Cardholder Authentication Field,” filed on Jun. 4, 2001; U.S. Provisional Patent Application No. 60/307,575, entitled “Method and System for Conducting Transactions Over a Communication Network Using a Secure Payment Application,” filed on Jul. 24, 2001; U.S. patent application Ser. No. 09/886,486, entitled “Method and System for Conducting Secure Payments Over a Computer Network Without a Pseudo or Proxy Account Number,” filed on Jun. 22, 2001; U.S. patent application Ser. No. 09/886,485, entitled “Method and System for Conducting Secure Payments Over a Computer Network,” filed on Jun. 22, 2001; U.S. patent application Ser. No. 10/096,271, entitled “System and Method for Conducting Secure Payment Transactions,” filed on Mar. 11, 2002; and U.S. Provisional Patent Application No. 60/352,968, entitled “MasterCard UCAF TM and SPA TM Client-less Solution,” filed on Jan. 30, 2002.
First, the Issuer Access Control Server creates a Message Authentication Code (MAC) (Step 402) in accordance with the procedures described in U.S. Provisional Patent Application No. 60/477,187, entitled “Algorithm for use in a Secure Payment Application,” filed on Jun. 10, 2003, and incorporated by reference hereinabove. Next, the Issuer Access Control Server sets the Application Authentication Value (AVV) Authentication Method variable to a value of “3” (Step 404), which indicates that voice authentication was performed for this transaction. The Issuer Access Control Server then includes the AVV in the Cardholder Authentication Verification Value (CAVV) field of the PARes message and sets the CAVV Algorithm field to a value of “3” to indicate that this is a Secure Payment Application AAV (SPA AVV) (Steps 406 and 408).
Next the Issuer Access Control Server generates a 3-D Secure certificate in accordance with the manner described in the 3-D Secure protocol (Step 410). The Issuer Access Control Server then sends the 3-D Secure certificate to an Authentication History Server, such as MasterCard®'s Authentication History Server, for records management purposes (Step 412) and sends the PARes message to the merchant via the merchant plug-in (Step 414). The merchant next verifies the 3-D Secure certificate, extracts the PARes data supplied by the Interface Application, and begins to generate an authorization request by inserting the AAV data in the Universal Cardholder Authentication Field (UCAF) (Step 416). The merchant then transmits the generated authentication message to the Acquirer (Step 418). The Acquirer responds by setting a Security Level Indicator (SLI) in the manner disclosed by the 3-D Secure protocol, and forwards the authorization request to the appropriate Issuer (Step 420). The Issuer next checks for the presence of the UCAF and may optionally verify the AAV, and then transmits an authorization response to the Acquirer (Step 422). Finally, the Acquirer sends the Issuer authorization response to the merchant (Step 422). The merchant should then send payment confirmation to the Cardholder using its normal business processes.
FIGS. 5 and 6 illustrate typical computer hardware suitable for practicing the present invention. Referring to FIG. 5, the computer system includes a processing section 510, a display 520, a keyboard 530, and a communications peripheral device 540 such as a modem. The system can also include a printer 560. The computer system typically includes one or more disk drives 570 which can read and write to computer-readable media such as magnetic media (i.e., diskettes) and/or optical media (e.g., CD-ROMS or DVDs), for storing data and application software. The system also typically includes an internal computer-readable medium 580 such as a hard disk drive. Other input devices, such as a digital pointer 590 (e.g., a mouse) and a card reader 550 for reading a payment card 500 can also be included. Computer hardware such as is illustrated in FIGS. 5 and 6 can be used to run the software illustrated in FIGS. 1-4, and/or can be used to perform functions of a computer processors utilized by consumer 102, merchant 104 (and the related merchant plug-in discussed hereinabove), acquirer 106, issuer system 108, and directory system 110.
providing payment account information associated with said payment account via telephone, said payment account information to be used for conducting said transaction;
5. The method of claim 1 wherein said authentication request includes at least a device category data field, an authentication request channel data field, a cardholder phone number data field and a voice channel transfer method data field.
6. The method of claim 1 further comprising the step of prompting the holder for authorization to complete the transaction.
7. A method for conducting a secure transaction using voice authentication wherein payment is processed from a holder's payment account comprising:
receiving payment account information associated with said payment account via telephone, said payment account information to be used for conducting said transaction;
8. The method of claim 7 further comprising the step of receiving an authentication response responsive to said authentication request.
9. The method of claim 8 further comprising the step of processing payment from said payment account to complete the transaction as a function of said authentication response.
10. The method of claim 8 wherein said authentication response is formatted according to the 3-D Secure authentication protocol.
11. The method of claim 7 wherein said authentication request includes at least a device category data field, an authentication request channel data field, a cardholder phone number data field and a voice channel transfer method data field.
12. The method of claim 7 further comprising the step of prompting the holder for authorization to complete the transaction.
13. A method for conducting a secure transaction using voice authentication wherein payment is processed from a payment account comprising:
14. The method of claim 13 further comprising the step of providing an authentication response responsive to said authentication request.
15. The method of claim 14 further comprising the step of processing payment from said payment account to complete the transaction as a function of said authentication response.
16. The method of claim 14 wherein said authentication response is formatted according to the 3-D Secure authentication protocol.
17. The method of claim 13 wherein said authentication request includes at least a device category data field, an authentication request channel data field, a cardholder phone number data field and a voice channel transfer method data field.
18. The method of claim 13 further comprising the step of prompting the holder for authorization to complete the transaction.
19. A system for conducting a secure transaction using voice authentication, comprising:
wherein said server computer subsystem determines if the payment account participates in voice authentication services, further wherein said automated voice response subsystem connects a call to said account holder to obtain a second voice sample of said account holder's voice, and further wherein said voice authentication subsystem compares said first voice sample to said second voice sample to determine whether the transaction is authorized by said account holder, and
wherein said automated voice response subsystem receives an authentication request, wherein said payment account information is provided via telephone and further wherein said authentication request is formatted according to the 3-D Secure authentication protocol.
20. The system for conducting a secure transaction using voice authentication of claim 19, wherein said automated voice response subsystem transmits an authentication response and further wherein said authentication response is formatted according to the 3-D Secure authentication protocol.
US12044304 2003-01-23 2008-03-07 System and method for secure telephone and computer transactions using voice authentication Active 2026-04-10 US8555358B2 (en)
US10764099 Continuation US7360694B2 (en) 2003-01-23 2004-01-23 System and method for secure telephone and computer transactions using voice authentication
US20080155655A1 true true US20080155655A1 (en) 2008-06-26
US8555358B2 US8555358B2 (en) 2013-10-08
US20040243514A1 (en) 2004-12-02 application