AU772372B2 - System and method for global internet digital identification - Google Patents
System and method for global internet digital identification Download PDFInfo
- Publication number
- AU772372B2 AU772372B2 AU78593/00A AU7859300A AU772372B2 AU 772372 B2 AU772372 B2 AU 772372B2 AU 78593/00 A AU78593/00 A AU 78593/00A AU 7859300 A AU7859300 A AU 7859300A AU 772372 B2 AU772372 B2 AU 772372B2
- Authority
- AU
- Australia
- Prior art keywords
- network
- authorization
- digital
- response message
- holder
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
- G06Q20/4014—Identity check for transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/403—Solvency checks
- G06Q20/4037—Remote solvency checks
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
- Telephonic Communication Services (AREA)
Description
WO 01/27887 PCTIUS00/27458 1 SYSTEM AND METHOD FOR GLOBAL INTERNET DIGITAL
IDENTIFICATION
SPECIFICATION
FIELD OF THE INVENTION This invention relates to digital identification (hereinafter "digital ID") applications used to purchase goods or services.
BACKGROUND OF THE INVENTION A digital ID is a set of digital data associated with an individual or entity. The ID can be, for example, a digital document a digital certificate) which associates a digital key with the individual or entity. Digital ID applications for use over the Internet and elsewhere are proliferating. One model for digital ID applications allows a third party service provider on the Internet to perform an exchange with a cardholder accessing the third party site and to retrieve from the cardholder a digital ID that the service provider can then validate with a "central point" before providing service.
The service provider goes to the "central point" for each validation and is charged based on the level of assurance that the "central point" is prepared to provide 0.100 for a guarantee that digital ID is good for $100, 10 for a guarantee that digital ID is good for $1000, etc.).
Currently, some parties are attempting to fill a need for new hierarchical/trust models based on new commercial relationships. In contrast,.the present invention provides a unique system and method for performing a digital ID function using currently existing payment system building blocks (such as the "EMV" standard promulgated jointly by Europay International MasterCard International Incorporated, and Visa International Service Association, and the "SET" standard 004437655 2 promulgated by SET Secure Electronic Transaction, LLC) and currently existing credit/debit card payment system contractual relationships. It is assumed that the reader is familiar with the EMV and SET standards, which are described in detail in the EMV and SET "References" listed in the "Related References" section below. These documents are incorporated by reference.
It would be desirable to leverage existing investments and infrastructure to provide a unique system and method for providing digital ID applications.
It would also be desirable to enable banks with a way to issue digital IDs at an assurance level with which they are comfortable, without the investment required to set up a new infrastructure or without the requirement to join a new consortium.
It would also be desirable to simplify contractual relationships required for providing digital ID applications. Under the present invention, each digital ID issuer has one contractual relationship with a "central switch" and each service provider has one contractual relationship with the "central switch".
It would also be desirable to provide standardized assurance levels for service providers. With the present invention, issuers of digital IDs may choose to use some or all of the assurance levels.
i It would also be desirable to provide a digital ID application that provides a high level of authentication while, at the same time, allowing the digital ID holder to remain anonymous to a digital ID verification requestor.
SUMMARY OF THE INVENTION SeAccording to a first aspect, the present invention provides a method for verifying an identity of an ID holder, comprising the steps providing a central switch in communication with a first network and a second network; receiving, into the central switch, identification data from the first network, wherein the identification data has been provided by the ID holder and transmitted into the first network; 004437655 2a controlling the central switch to use the identification data to generate an authorization request message having a format suitable for transmission through the second network; controlling the central switch to transmit the authorization request message into the second network to an ID issuer; receiving, into the central switch, an authorization response message from the second network, wherein the authorization response message has been generated by the ID issuer in response to the authorization request message; controlling the central switch to use the authorization response message to generate an output response message having a format suitable for transmission through the first network; controlling the central switch to transmit the output response message into the first network; storing secret data which is shared with the ID holder; receiving, by the ID issuer, the authorization request message; using, by the ID issuer, the secret data to perform an authentication operation upon the authorization request message, thereby generating the authorization response message; and transmitting, by the ID issuer, the authorization response message through the second network to the central switch, wherein: the identification data includes a result of a first cryptographic operation; the authorization response message includes a result of a second cryptographic operation; the first network comprises an international network; o 25 the second network comprises a trusted network; the central switch comprises a secure electronic transaction gateway; *the authorization response message includes at least one of an indication of authorization and an indication of denial of authorization; 004437655 2b the authorization response message includes information about the ID holder; the authorization response message includes a password suitable for enabling the ID holder to access a web site; the identification data includes at least one of a payment amount field and a validation level amount field; the authorization request message has a 0100 chip format; the authorization response message has a 0110 format; the output response message has an EMV format; and the identification data does not include a payment account number, said method further comprising the steps of: issuing a digital ID to the ID holder, wherein the identification data is generated by the digital ID; using the output response message to decide whether to provide a service to the ID holder; using the secret data to generate a cryptographic transaction certificate; storing transaction data related to at least one of the identification data, the authorization request message, the authentication operation, the authorization go ee response message, and the output response message, said transaction data including said transaction certificate; o incorporating the transaction certificate into payment transaction data; using the payment transaction data to initiate a payment; collecting a fee from an ID requestor which has transmitted the identification data into the first network; and 25 distributing at least one share of the fee to at least one ID issuer.
According to a second aspect, the present invention provides a system for verifying an identity of an ID holder, comprising a central switch in communication with a first network and a second network, said central switch being configured to perform the steps of: 004437655 2c receiving identification data from the first network; using the identification data to generate an authorization request message having a format suitable for transmission through the second network; transmitting the authorization request message through the second network; receiving, from the second network, an authorization response message generated in response to the authorization request message; using the authorization response message to generate an output message having a format suitable for transmission through the first network; and transmitting the output message through the first network, the system further comprising an ID issuer configured to perform the steps of: storing secret data which is shared with the ID holder; receiving the authorization request message from the central switch, through the second network; using the secret data to perform an authentication operation upon the authorization request message, thereby generating the authorization response message; and transmitting the authorization response message to the central switch, through the second network, the system further comprising an ID requester, wherein: the identification data includes a result of a first cryptographic operation; the authorization response message includes a result of a second cryptographic operation; the first network comprises an international network; 25 the second network comprises a trusted network; the central switch comprises a secure electronic transaction gateway; e* the authorization response message includes at least one of an indication of authorization and an indication of denial of authorization; 004437655 2d the authorization response message includes information about the ID holder; the authorization response message includes a password suitable for enabling the ID holder to access a web site; the identification data includes at least one of a payment amount field and a validation level amount field; the authorization request message has a 0100 chip format; the authorization response message has a 0110 format; the output message has an EMV format; the identification data does not include a payment account number; the ID issuer is configured to issue a digital ID to the ID holder, wherein the identification data is generated by the digital ID; the ID requestor is configured to use the output message to decide whether to provide a service to the ID holder; at least one of the central switch and the ID issuer is further configured to store transaction data related to at least one of the identification data, the authorization request message, the authentication operation, the authorization response message, and the output response message, said transaction data including a cryptographic transaction certificate; at least one of the central switch and the ID issuer is further configured to perform the steps of: incorporating the transaction certificate into payment transaction data; and using the payment transaction data to initiate a payment; and the central switch is further configured to perform the steps of: .i 25 collecting a fee from the ID requester; and distributing at least one share of the fee to at least one ID issuer.
o:ie BRIEF DESCRIPTION OF THE DRAWING Further objects, features, and advantages of the invention will become apparent from the following detailed description taken in conjunction with the WO 01/27887 PCT/US00/27458 3 accompanying figure showing illustrative embodiments of the invention, in which: FIG. 1 is a diagram of information flow in an exemplary system for performing digital ID in accordance with the invention.
In the figure, unless otherwise stated, the same reference numerals and characters are used to denote like features, elements, components, or portions of the illustrated embodiments. Moreover while the subject invention will now be described in detail with reference to the figure and in connection with the illustrative embodiments, changes and modifications can be made to the described embodiments without departing from the true scope and spirit of the subject invention as defined by the appended claims.
DETAILED DESCRIPTION OF THE INVENTION According to the present invention, a digital ID issuer issues a digital ID to a digital ID holder. When a party desires to authenticate a digital ID holder, the request for digital ID verification is routed to the digital ID issuer over a distributed communication network. The distributed communication network may include the Internet and an existing legacy payment system infrastructure (such as the Banknet infrastructure of MasterCard International Incorporated). The Internet and the existing legacy payment system infrastructure are connected by a "central switch" or gateway (such as a SET gateway).
Digital ID holders are, with the present invention, able to anonymously identify themselves in remote environments, such as the Internet, to other parties. The digital ID is a portable identity object that is simple for digital ID holders to use and can eliminate the need by digital ID holders to remember different passwords and user-ID combinations required to gain access to protected Internet sites. While not revealing any other details of the identity to the identity verification requester, the present invention can release only agreed identity data to the identity verification requester. It is the digital ID issuer who provides and controls all data.
In transmitting the request for digital ID verification, the present invention uses a set of separate, stand-alone, non-payment messages which utilize existing legacy payment system message formats and payment-related data. The digital ID WO 01/27887 PCT/US00/27458 4 verification request involves the use of a shared secret (of any type) possessed only by the digital ID issuer and the digital ID holder. High security is enabled since the number and types of secrets shared and algorithms used by the parties are varied and potentially non-standard. The digital ID issuer will receive and validate a digital ID payment object, which is created by the digital ID holder with the shared secret.
Advantageously, the digital ID payment object is passed as an opaque block (an object that cannot be read) through all intermediary nodes to the digital ID issuer.
When a digital ID issuer receives a digital ID verification request, the digital ID issuer has a number of response options available to it. One option is to simply respond with a binary "yes" or "no" to the digital ID verification request. A second option is to respond with other data which is related to the digital ID holder, such as demographic data, payment history data, and/or other marketing data. Preferably, this other data is non-personally identifiable data, and the dissemination of this other data is pre-approved by the digital ID holder. The data may also include passwords for accessing a service provider's web site.
Previous digital identification technology has employed asymmetric key technology with private/public key pairs and digital certificates, sometimes combined with secured integrated circuit (IC) chip cards. Advantageously, the present invention can be deployed without chip cards or any secure hardware deployed by the digital ID issuer. Moreover, the present invention may use shared symmetric key technology, instead of asymmetric key technology, to provide a digital ID function.
Another unique feature of the present invention is that digital ID verification may occur before and/or after a payment transaction, and the digital ID verification is capable of being linked with the payment transaction through cryptography. The linking is accomplished through the use of a cryptogram, which is an object containing the result of a cryptographic operation. Preferably, the present invention uses time-sensitive data.
A preferred embodiment of the present invention will now be described. In this preferred embodiment, the basic cryptographic techniques utilize parts of the EMV credit or debit payment specification and an EMV infrastructure. An EMVcompliant chip card may be used with this embodiment, but (as already mentioned) WO 01/27887 PCT/US00/27458 chip card use is not required. Instead, an digital ID application may be stored, for example, on a computer that is connected to the Internet. The stored digital ID application stored on the computer could function as a "virtual" chip card.
With reference to Fig. 1, a digital ID issuer 500 (such as a bank) preferably issues a physical or virtual chip card 100 based on the EMV specification. The chip card 100 can, optionally, be direct mailed to an end user. The chip card 100 may contain a single application or multiple applications on it, and can, optionally, be based on the MULTOSTM operating system or on another operating system. It is assumed that the reader is familiar with the MULTOSTM standard, which is maintained by the MAOSCO Consortium. The standard is described in the MULTOSTM "References" listed in the "Related References" section below. These documents are incorporated by reference.
The digital ID issuer 500 assigns a payment-related or non-payment-related digital ID account number within the MasterCard Payment Application (MCPA) function in the chip card 100. However, the digital ID account number is not required to be a credit/debit card account number (and, indeed, for security purposes, it is preferred that the digital ID not be such a number). In essence, the digital ID issuer may deploy digital ID EMV-based applications which do not use credit/debit card account numbers but assign an account number only for digital ID use.
After the digital ID is issued, the cardholder logs onto the Intemrnet and requests a service from a service provider web site (this request represented by arrow 1 of Fig.
1).
Before providing the requested service, the service provider 200 may decide to verify the cardholder's identity. It is up to the service provider to decide the frequency with which it requests verification from its customers. The service provider may request verification each and every time a service is requested, or it may request verification only occasionally.
If the service provider 200 decides to request verification, the service provider preferably initiates a SET specification based transaction (for confidentiality and integrity of messaging over the Intemrnet) and asks the cardholder (this request represented by arrow 2 of Fig. 1) to use its chip card (virtual or physical) to initiate a WO 01/27887 PCT/US00/27458 6 digital ID verification transaction (shown as arrow The digital ID verification transaction uses the credit/debit payment message formats of the MCPA and EMV specifications. These message formats may be used in a number of ways. For example, the payment amount field may be set to zero and the request may be treated as an authorization for a payment transaction of zero amount. Alternatively, a new message type may be added (for example, a "digital ID request" type) to the existing payment infrastructure. This new message type can be used to redefine certain fields.
In particular, the payment field may no longer represent a payment amount, but a validation level amount. For example, if the payment field contains $100, the digital ID issuer will validate the identity of the digital ID at this validation level.
When a cardholder receives a request to initiate a digital ID verification transaction, the cardholder produces an EMV-formatted cryptogram (shown as arrow 3) (such as an authorization request cryptogram or an "ARQC" cryptogram) and provides it to the service provider 200. The cryptogram is then transported (arrow 4) securely over the Internet, protected by (for example) the SET protocol. The cryptogram can be a digital certificate.
The service provider passes this transaction request (arrow 4) over the Internet, using (preferably) the SET protocol, to a "central switch" 300, which may provide a SET payment gateway function. Since the transaction is not a payment, a bankprovided payment gateway is not necessary. The central switch 300 can, optionally, be a SET acquirer.
The switch 300 reformats the verification transaction request to the format for message transmission over a trusted back-end network 400 (such as MasterCard International Inc.'s Banknet network). For example, if the back-end network is MasterCard International Inc.'s Banknet network, the verification request message is formatted as a "0100" chip formatted authorization request message. The reformatted message is then passed (arrow 5) into the trusted back-end network 400, which routes the verification request (arrow 6) to the digital ID issuer 500.
The digital ID issuer 500 authenticates the digital ID verification transaction and stores the transaction for possible service provider fee collection at a level identified and requested on the verification request message. As previously discussed, WO 01/27887 PCT/US00/27458 7 the response by the digital ID issuer may be a simple "yes" or "no" or it may include other digital ID holder-related data. The response also preferably includes an Authorization Response Cryptogram ("ARPC").
The digital ID issuer 500 responds to the switch via the trusted back-end network 400 with an authorization response message (arrow If the back-end network is MasterCard's Banknet network, the message is a "0110" formatted authorization response message. It is formatted as a payment authorization request but carries digital ID response data. The back-end network 400 then passes the message (arrow 8) to the switch 300.
The switch formats the authorizationresponse message as a SET/EMV response message (arrow 9) to the service provider 200. The response message confirms or denies the digital ID authentication at the requested service level. This response message is similar to an authorization for purchase response.
When the service provider 200 receives the SET/EMV response message, it decides whether to provide service to the cardholder. The service provider may optionally complete the EMV-like transaction by sending a SET message (arrow back to the physical or virtual card.
The functions of the switch system are as follows: 1. Receive and translate SET/EMV messages on the Internet from service providers into 0100 payment formatted messages for Banknet.
2. Identify and translate 0110 formatted messages from Banknet into SET/EMV messages on the Internet to service providers.
3. Identify and log transactions for fee purposes.
4. Gather fees from service providers.
5. Distribute shares of fees to digital ID issuers.
6. Identify new contents of fields on 0100/0110 messages and SET/EMV messages to facilitate identification or non-payment transaction.
WO 01/27887 PCT/US00/27458 8 To ensure the freshness of a digital ID request and avoid replay of a digital ID request at a later date and time, it is preferred that digital ID devices will generate a random number challenge which is used, along with other data, by the digital ID holder to create the digital ID cryptogram sent to the digital ID issuer for validation.
A preferred embodiment is to use SET technology and EMV chip card technology for this function.
A preferred embodiment of the present invention is built upon the EMV electronic commerce specification but includes the following modifications and additions. The digital ID number is preferably a fully "routable" credit or debit primary account number (PAN), but the number is not necessarily related to a payment account. In a preferred embodiment, the digital ID number is not the account number used for payment.
In addition, the present invention also adds the option to save the EMV final Transaction Certificate (TC) by the cardholder system. This final TC (arrow 11) is a cryptographic object that may be used to link a digital ID verification transaction to a payment transaction. The TC is based on the same shared secret as that used in generating the ARQC and on the ARPC received from the digital ID issuer. In those cases when the digital ID issuer is the same as the payment account issuer, the TC (along with the data needed to generate the TC) provides a strong linkage between the digital ID verification transaction and a payment authorization request. To achieve the linkage, the TC may be bundled into a payment transaction as the "random number" used in the initiate payment transaction stage. An advantage to using the TC in this manner is that a lower level of security is needed to transmit the payment transaction data over the Internet. This is because the transaction route has already been verified by the digital ID verification transaction and the receipt of an ARPC.
Although the present invention has been described in connection with particular embodiments thereof, it is to be understood that such embodiments are susceptible of modification and variation without departing from the scope of the inventive concept as defined by the appended claims.
WO 01/27887 PCT/US00/27458 9 RELATED REFERENCES The following references are hereby incorporated by reference in their entireties: SET References: SET Secure Electronic Transaction Specification. Book I: Business Description, Version 1.0, May 31, 1997 (available at http://www.setco.org/download.html).
SET Secure Electronic Transaction Specification Book 2: Programmer's Guide, Version 1.0, May 31, 1997 (available at http://www.setco.org/download.html).
SET Secure Electronic Transaction Specification Book 3: Formal Protocol Definition, Version 1.0, May 31, 1997 (available at http://www.setco.org/download.html).
SET Glossary of Terms, July 1999 (available at http://www.setco.org/download.html).
External Interface Guide to SET Secure Electronic Transaction, September 24, 1997 (available at http://www.setco.org/download.html).
SET Generic Cryptogram Extension, July 19, 1999 (available at http://www.setco.org/download.html).
SET Japanese Payment Option Extension, August 24, 1999 (available at http://www.setco.org/download.html).
SET Merchant Initiated Authorization Extension, July 19, 1999 (available at http://www.setco.org/download.html).
SET Online PIN Extensions, July 19, 1999 (available at http://www.setco.org/download.html).
SET CW2/CVC2 Extension, September 29, 1999 (available at http://www.setco.org/download.html).
WVO 01/27887 PCT/USOO/27458 EMV References: EMI''96 Chip Electronic Commerce Specification, Draft 1.0, 1999.
EMV '96 Integrated Circuit Card Specification for Payment Systems, Version 3. 1. 1, May 31, 1998 (available at http://www.emvco.com/specificauions.cfin).
EMVl 96 Integrated Circuit Card Terminal Specification for Payment Systems, Version 3. 1. 1, May 31, 1998 (available at http://www.emvco.com/specifications.cfm).
EMV '96 Integrated Circuit Card Application Specification for Payment Systems, Version 3. 1. 1, May 31, 1998 (available at http://www.emvco.com/specifications.cfmn).
Business Functional Requirements for Debit and Credit on Chip, Version October 20. 1997 (available at http://www.mastercard.comi/emv/emvspecs02.html#emv2).
Integrated Circuit Card Application Specifications for Debit and Credit on Chip, Version 2.0, November 1998 (available at http://www.mastercard.com/emv/emvspecs02.html#emv2).
Minimumn Card Requirements for Debit and Credit on Chip, Version 2.0, November 1998 (available at http://www.mastereard.com/emv/emvspecs02.html#emv2).
Terminal Requirements for Debit and Credit on Chip, Version 2.0, November 1998 (available at http://www.mastercard.com/emv/emvspecs02.htmil#emv2).
Integrated Circuit Card Terminal Application Services Type Approval, Version October 24, 1997 (available at bttp://www.mastercard.com/emv/emvspecs02.html#emv2).
Personalization Data Specifications for Debit and Credit on Chip, Version August 1998 (available at http://www.mastercard.com/emv/emvspecs02.html#emv2).
WO 01/27887 WO 0127887PCTIUSOO/27458 MULTOS References: MAOSCO, A Guide to the MULTOS Scheme (2000).
MAOSCO, Information Bulletin Introduction to MUL TOS MA OSCO, Jan. 4, 1998 (available at http://dh0O7-00.web.dircon.net/present.ihtml).
MAOSCO, Information Bulletin 6 MAO4SCO Policy Position on ITSEC Matters, Mar. 19, 1999 (available at http://dh0O7-O.web.dircon.net/present.ihtml).
MAOSCO, Information Bulletin No. 3 Developing Loading Applications, Mar.
1998 (available at http://dh007-OO.web.dircon.net/present. ihtmli).
MAOSCO, Information Bulletin No. 4 Using MULTOS, Apr. 1998 (available at MAOSCO, Information Bulletin No S Application Load/Delete Certificates Application Load Units, March 18, 1998 (available at http:H/dhOO7- 00.web.dircon.net/present.ihtml).
MAOSCO, Information Bulletin No. 7 -Export Controls, Sept. 29, 1998 (available at http://dh007-0.web.dircon.net/present.ihtrni).
MAOSCO, Information Bulletin No. 8 -Obtaining an Implementation Licence, May 14, 1998 (available at http://dh007-OO.web.dircon.net/present.ihtml).
MAOSCO, Information Bulletin No. 9 -Export Controls, End-User Undertaking Guidance, Mar. 4, 1999 (available at MAOS CO, Technical Bulletin No. I Shell Applications, Apr. 15, 1999 (available at http://dh007-O0.web.dircon.net/present.ihtml).
MAOSCO, Technical Bulletin No. 2 MULTOS and ISO 7816 Files, Jul. 7, 1998 (available at http://dh007-O0.web.dircon.net/present.ihtml).
MACSCO, Technical Bulletin No. 4 Enablernent/MSM Controls Data Loading, WO 01/27887 PCT1US00127458 12 Dec. 4, 1998 (available at http://dhOO7-OO.web-dircon.net/present.ihtm).
MAOSCO. Technical Bulletin No. 5 Delegation, Apr. 15, 1999 (available at http://dhOO7-OO.web.dircon.net/present.ihtml).
MAOSCO, Technical Bulletin No. 6 What's New in MULTOS, Sept. 1, 1998 (available at http://dhOO7-OO.web.dircon.net/present.ihtml).
Claims (3)
- 2. A system for verifying an identity of an ID holder, comprising a central switch in communication with a first network and a second network, said central switch being configured to perform the steps of: receiving identification data from the first network; using the identification data to generate an authorization request message having a format suitable for transmission through the second network; transmitting the authorization request message through the second network; receiving, from the second network, an authorization response message generated in response to the authorization request message; using the authorization response message to generate an output message having a format suitable for transmission through the first network; and transmitting the output message through the first network, the system further comprising an ID issuer configured to perform the steps of: storing secret data which is shared with the ID holder; receiving the authorization request message from the central switch, through the second network; *using the secret data to perform an authentication operation upon the authorization request message, thereby generating the authorization response message;and Setransmitting the authorization response message to the central switch, through the second network, the system further comprising an ID requester, wherein: 25 the identification data includes a result of a first cryptographic operation; the authorization response message includes a result of a second cryptographic operation; the first network comprises an international network; the second network comprises a trusted network; 004437655 16 the central switch comprises a secure electronic transaction gateway; the authorization response message includes at least one of an indication of authorization and an indication of denial of authorization; the authorization response message includes information about the ID holder; the authorization response message includes a password suitable for enabling the ID holder to access a web site; the identification data includes at least one of a payment amount field and a validation level amount field; the authorization request message has a 0100 chip format; the authorization response message has a 0110 format; the output message has an EMV format; the identification data does not include a payment account number; the ID issuer is configured to issue a digital ID to the ID holder, wherein the identification data is generated by the digital ID; the ID requestor is configured to use the output message to decide whether to provide a service to the ID holder; at least one of the central switch and the ID issuer is further configured to 0: store transaction data related to at least one of the identification data, the 20 authorization request message, the authentication operation, the authorization 0 response message, and the output response message, said transaction data including a cryptographic transaction certificate; at least one of the central switch and the ID issuer is further configured to e0ee perform the steps of: 25 incorporating the transaction certificate into payment transaction data; and using the payment transaction data to initiate a payment; and e0*e the central switch is further configured to perform the steps of: collecting a fee from the ID requester; and distributing at least one share of the fee to at least one ID issuer. 004437655 17
- 3. A method for verifying an identity of an ID holder including the steps substantially as hereinbefore described with reference to the accompanying drawing.
- 4. A system for verifying an identity of an ID holder substantially as hereinbefore described with reference to the drawing. MasterCard International Incorporated By its Patent Attorneys Freehills Carter Smith Beadle 23 February 2004 S S*
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US15860899P | 1999-10-08 | 1999-10-08 | |
| US60/158608 | 1999-10-08 | ||
| US16388699P | 1999-11-05 | 1999-11-05 | |
| US60/163886 | 1999-11-05 | ||
| PCT/US2000/027458 WO2001027887A1 (en) | 1999-10-08 | 2000-10-05 | System and method for global internet digital identification |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| AU7859300A AU7859300A (en) | 2001-04-23 |
| AU772372B2 true AU772372B2 (en) | 2004-04-22 |
Family
ID=26855201
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| AU78593/00A Ceased AU772372B2 (en) | 1999-10-08 | 2000-10-05 | System and method for global internet digital identification |
Country Status (6)
| Country | Link |
|---|---|
| EP (1) | EP1218861A1 (en) |
| JP (1) | JP2003511802A (en) |
| AU (1) | AU772372B2 (en) |
| CA (1) | CA2385954C (en) |
| HK (1) | HK1047337A1 (en) |
| WO (1) | WO2001027887A1 (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB0020108D0 (en) * | 2000-08-15 | 2000-10-04 | Nokia Mobile Phones Ltd | Devices |
| US20030217148A1 (en) * | 2002-05-16 | 2003-11-20 | Mullen Glen H. | Method and apparatus for LAN authentication on switch |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5557518A (en) * | 1994-04-28 | 1996-09-17 | Citibank, N.A. | Trusted agents for open electronic commerce |
| US5826245A (en) * | 1995-03-20 | 1998-10-20 | Sandberg-Diment; Erik | Providing verification information for a transaction |
| EP0921487A2 (en) * | 1997-12-08 | 1999-06-09 | Nippon Telegraph and Telephone Corporation | Method and system for billing on the internet |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2100134C (en) * | 1992-09-29 | 1999-06-22 | Raymond Otto Colbert | Secure credit/debit card authorization |
| US5590197A (en) * | 1995-04-04 | 1996-12-31 | V-One Corporation | Electronic payment system and method |
| FR2733068B1 (en) * | 1995-04-14 | 1997-07-04 | G C Tech | ELECTRONIC PAYMENT METHOD FOR PERFORMING TRANSACTIONS RELATED TO THE PURCHASE OF GOODS ON A COMPUTER NETWORK |
| US5757917A (en) * | 1995-11-01 | 1998-05-26 | First Virtual Holdings Incorporated | Computerized payment system for purchasing goods and services on the internet |
| US5943424A (en) * | 1996-06-17 | 1999-08-24 | Hewlett-Packard Company | System, method and article of manufacture for processing a plurality of transactions from a single initiation point on a multichannel, extensible, flexible architecture |
| US5903882A (en) * | 1996-12-13 | 1999-05-11 | Certco, Llc | Reliance server for electronic transaction system |
| US5883810A (en) * | 1997-09-24 | 1999-03-16 | Microsoft Corporation | Electronic online commerce card with transactionproxy number for online transactions |
| US5991750A (en) * | 1997-10-24 | 1999-11-23 | Ge Capital | System and method for pre-authorization of individual account transactions |
-
2000
- 2000-10-05 AU AU78593/00A patent/AU772372B2/en not_active Ceased
- 2000-10-05 WO PCT/US2000/027458 patent/WO2001027887A1/en active IP Right Grant
- 2000-10-05 JP JP2001530828A patent/JP2003511802A/en active Pending
- 2000-10-05 CA CA002385954A patent/CA2385954C/en not_active Expired - Lifetime
- 2000-10-05 EP EP00968720A patent/EP1218861A1/en not_active Ceased
-
2002
- 2002-12-11 HK HK02108987.6A patent/HK1047337A1/en unknown
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5557518A (en) * | 1994-04-28 | 1996-09-17 | Citibank, N.A. | Trusted agents for open electronic commerce |
| US5826245A (en) * | 1995-03-20 | 1998-10-20 | Sandberg-Diment; Erik | Providing verification information for a transaction |
| EP0921487A2 (en) * | 1997-12-08 | 1999-06-09 | Nippon Telegraph and Telephone Corporation | Method and system for billing on the internet |
Also Published As
| Publication number | Publication date |
|---|---|
| JP2003511802A (en) | 2003-03-25 |
| EP1218861A1 (en) | 2002-07-03 |
| CA2385954A1 (en) | 2001-04-19 |
| WO2001027887A1 (en) | 2001-04-19 |
| HK1047337A1 (en) | 2003-02-14 |
| AU7859300A (en) | 2001-04-23 |
| CA2385954C (en) | 2008-05-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6681328B1 (en) | System and method for global internet digital identification | |
| US7680736B2 (en) | Payment system | |
| US6941285B2 (en) | Method and system for a virtual safe | |
| US8175973B2 (en) | Internet payment, authentication and loading system using virtual smart card | |
| US6889325B1 (en) | Transaction method and system for data networks, like internet | |
| US20010047335A1 (en) | Secure payment method and apparatus | |
| EP1687725B1 (en) | Secure payment system | |
| AU2001248198A1 (en) | A method and system for a virtual safe | |
| CA2371168A1 (en) | Transaction method and system for data networks, like internet | |
| AU772372B2 (en) | System and method for global internet digital identification | |
| KR100458526B1 (en) | System and Method for the wire·wireless complex electronic payment | |
| ZA200202364B (en) | System and method for global internet digital identification. | |
| Jarupunphol et al. | The future of SET | |
| AU2011203165B2 (en) | Secure payment system | |
| Watson | Electronic cash and set | |
| Pfitzmann et al. | Smartcard-Supported Internet Payments | |
| KR20040088111A (en) | System and Method for Payment by Using Intelligent Smart Card | |
| KR20080036175A (en) | Ic chip | |
| KR20080036174A (en) | Method for payment by using intelligent smart card |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FGA | Letters patent sealed or granted (standard patent) |