EP1076875B1 - Procede et appareil de personnalisation et de synchronisation dynamique de carte a puce - Google Patents

Procede et appareil de personnalisation et de synchronisation dynamique de carte a puce Download PDF

Info

Publication number
EP1076875B1
EP1076875B1 EP99920324A EP99920324A EP1076875B1 EP 1076875 B1 EP1076875 B1 EP 1076875B1 EP 99920324 A EP99920324 A EP 99920324A EP 99920324 A EP99920324 A EP 99920324A EP 1076875 B1 EP1076875 B1 EP 1076875B1
Authority
EP
European Patent Office
Prior art keywords
smartcard
card
communicate
data
enterprise
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.)
Expired - Lifetime
Application number
EP99920324A
Other languages
German (de)
English (en)
Other versions
EP1076875A1 (fr
EP1076875A4 (fr
Inventor
William Hohle
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
American Express Travel Related Services Co Inc
Original Assignee
American Express Travel Related Services Co Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by American Express Travel Related Services Co Inc filed Critical American Express Travel Related Services Co Inc
Publication of EP1076875A1 publication Critical patent/EP1076875A1/fr
Publication of EP1076875A4 publication Critical patent/EP1076875A4/fr
Application granted granted Critical
Publication of EP1076875B1 publication Critical patent/EP1076875B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

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
    • G07F7/10—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 together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
    • G07F7/1008—Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K17/00—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/355—Personalisation of cards for use
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • G06Q20/3672—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes initialising or reloading thereof
    • 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/409—Device specific authentication in transaction processing
    • G06Q20/4093—Monitoring of device authentication

Definitions

  • the present invention relates, generally, to the use of integrated circuit cards (“smartcards”) for commercial transactions and, more particularly, to techniques for dynamically synchronizing and personalizing smartcard information in the context of a distributed transaction system.
  • smartcards integrated circuit cards
  • smartcards are wallet-sized (or smaller) cards incorporating a microprocessor or microcontroller to store and manage data within the card. More complex than magnetic-stripe and stored-value cards, smartcards are characterized by sophisticated memory management and security features. Multifunction cards, for example, are often configured to support credit, debit, stored value, loyalty, and a number of other applications all within a single card.
  • a typical multi-function smartcard includes a microcontroller embedded within the card plastic which is electrically connected to an array of external contacts provided on the card exterior.
  • the smartcard microcontroller generally includes an electrically-erasable and programmable read only memory (EEPROM) for storing user data, random access memory (RAM) for scratch storage, and read only memory (ROM) for storing the card operating system.
  • EEPROM electrically-erasable and programmable read only memory
  • RAM random access memory
  • ROM read only memory
  • Relatively simple microcontrollers are adequate to control these functions.
  • ISO 7816-1 Part 1: Physical characteristics (1987); ISO 7816-2, Part 2: Dimensions and location of the contacts (1988); ISO 7816-3, Part 3: Electronic signals and transmission protocols (1989, Amd. 1 1992, Amd, 2 1994); ISO 7816-4, Part 4: Inter-industry commands for interchange (1995); ISO 7816-5, Part 5: Numbering system and registration procedure for application identifiers (1994, Amd.
  • present systems are inadequate in that the systems often do not allow an enterprise, such as a smartcard corporate partner (for example, Hertz, Hilton and the like) to dynamically add to or otherwise modify the smartcard application structure itself. That is, in the context of multi-function cards, it is often infeasible to alter or augment the card's file structure without engaging in the time-consuming and costly process of re-issuing the card.
  • a smartcard corporate partner for example, Hertz, Hilton and the like
  • a smartcard often contains a number of different applications associated with a wide range of enterprise organizations.
  • the writing, updating, and reading of these files is advantageously restricted to particular parties in accordance with a set of access condition rules.
  • These access conditions are suitably implemented using cryptographic keys which are known only to the appropriate parties, such as the enterprise.
  • a card issuing party such as American Express will typically not have access to the keys necessary to perform its function.
  • Known systems have attempted to solve this problem by accumulating key data in a central repository used in the issuance process. This method is unsatisfactory in a number of respects. Most notably, a security breach in the central repository of key information would have disastrous consequences.
  • WO 97/39424 describes a system and apparatus for smart card personalisation. It includes a smart card personalisation system that maintains a database containing card issuer data format templates, card applications, card operating systems commands and personalisation equipment specifications. The system is adapted to provide a centralised interface of inputs and outputs to a card issuing process which dynamically adjusts to changes in the issuing process to easily permit a card issuer to change the formats, card applications, card operating systems and/or personalisation equipment in a card issuing process.
  • EP 0 836 160 which describes a method and system for limiting adverse use of counterfeit credit cards, access badges, electronic accounts or the like.
  • the system is adapted to enable a rejection of second and subsequent copies of an informally-equivalent card or badge inserted into a client/server system by processing only those cards that have transaction histories recorded thereon.
  • the present invention overcomes the limitations of the prior art by providing methods and apparatus for personalizing and synchronizing smartcard data in the context of a distributed transaction system.
  • a dynamic smartcard synchronization system comprises access points configured to initiate a transaction in conjunction with a smartcard, an enterprise data collection unit, and a card object database update system.
  • An exemplary dynamic synchronization system preferably comprises various smartcard access points, a secure support client server, a card object database update system (CODUS), one or more enterprise data synchronization interfaces (EDSI), an update logic system, one or more enterprise data collection units. (EDCUs), and one or more smartcard access points configured to interoperably accept and interface with smartcards.
  • DSS comprises a personalization system and an account maintenance system configured to communicate with CODUS.
  • personalization of multi-function smartcards is accomplished using a security server configured to generate and/or retrieve cryptographic key information from multiple enterprise key systems during the final phase of the smartcard issuance process.
  • an exemplary dynamic synchronization system preferably comprises a secure support client server 104, a card object database update system 106 (CODUS), one or more enterprise data synchronization interfaces 108 (EDSI), an update logic system 110, one or more enterprise data collection units 112 (EDCUs), and one or more smartcard access points 102 configured to interoperably accept and interface with smartcards 120.
  • DSS also suitably comprises a personalization system 140 and an account maintenance system 142 configured to communicate with CODUS 106.
  • secure support client server 104 is connected over a suitable network to EDSIs 108 through enterprise networks 114.
  • EDSIs 108 are linked to update logic system 110, which itself is linked to enterprise data collection units 112.
  • Enterprise data collection units 112 are linked to CODUS 106 and secure support client server 104.
  • each enterprise e.g., airline partner, hotel partner, travel agency, etc.
  • each enterprise is preferably associated with a corresponding EDSI 108, enterprise network 114, and EDCU 112.
  • EDCU 112(a) corresponds to EDSI 108(a) and enterprise network 114(a)
  • EDCU 112(b) corresponds to EDSI 108(b) and enterprise network 114(b)
  • the DSS may include an arbitrary number of such functional blocks in accordance with the number of enterprises represented.
  • Personalization system 140 suitably functions as the issuing source of smartcards 120. That is, personalization system 140 creates and issues smartcards for use by the consumer by providing a predetermined file structure populated with initialization data (e.g., account numbers, serial numbers, default preferences, and the like).
  • initialization data e.g., account numbers, serial numbers, default preferences, and the like.
  • CODUS 106 interfaces with personalization system 140 in order to facilitate reissuance of the card by providing updated data in the event a card is destroyed, lost, or stolen.
  • Personalization system 140 is described in detail below in conjunction with FIG. 9.
  • Account maintenance system 142 is provided for customer service purposes and, in this capacity, acts as the point of entry for cardholder complaints, questions, and other customer input.
  • CODUS 106 suitably communicates with account maintenance system 142 in order to assist customer service representatives and/or automated systems in addressing cardholder issues.
  • Smartcard access points 102 allow the cardholder to gain access to the distributed transactions system through a variety of means.
  • Such access points may include, for example, standard home telephones, various PCS wireless systems, pay phones, palmtop computers, notebook computers, Internet workstations, automated teller machines (ATMs), point of sale terminals (POS) stand-alone kiosks, network computers (NCs), personal data assistants (PDAs), or any other suitably configured communication apparatus.
  • Access points 102 may be portable (as in the case of PDAs and cellular phones) or centrally located, for example, in airline ticketing and gate areas, rental car facilities, hotel lobbies, travel agencies, and malls. In addition, businesses might see fit to host an access point 102 to streamline their employees' business travel.
  • various access points 102 are configured to interface with contact-based smartcards 120 in accordance with the relevant portions of the ISO-7816 standard.
  • Secure support client server 104 provides, where appropriate, any functionality missing from the individual access point 102 used during a transaction.
  • Server 104 also suitably handles routing of messages from access points 102 to the appropriate EDSI 108 and/or EDCU 112.
  • an exemplary secure support client server 104 comprises a security engine 202, a supplemental application support 204, and a router 206.
  • Security engine 202 comprises suitable hardware and/or software to provide secure messaging between server 104, EDSUs 112, and enterprise networks 114. More specifically, security engine 202 utilizes authentication, data encryption, and digital signature techniques in connection with incoming and outgoing message packets.
  • a variety of conventional security algorithms are suitable in the context of the present invention, including, for example, DES encryption, RSA authentication, and a variety of other symmetrical and non-symmetrical cryptographic techniques.
  • Supplemental application support 204 preferably comprises suitable hardware and/or software components related to a specific access point 102 functionality. More particularly, server 104 suitably determines the nature of the access point 102 utilized during a transaction. If the access point 102 does not include the appropriate software for effecting the requested transaction, then server 104 supplies the functionality (i.e., software modules) which completes the transaction with respective EDSIs 108 and/or EDCUs 112.
  • the supplemental functionality includes, inter alia, software modules for properly formatting message packets (described in further detail below) sent out over the various networks comprising the DSS.
  • server 104 need only transfer the various message packets to and from the access point 102 without supplying additional software.
  • Added functionality may be supplied through any suitable method, for example, through the use of portable software code (e.g., Java, ActiveX, and the like), or distributed software residing within access points 102, cards 120, and/or server 104.
  • Router 206 suitably handles routing of messages to the appropriate EDCUs 112, enterprise networks 114, and access points 102. That is, router 206 is configured to identify the appropriate functional blocks within the DSS to which a given message packet should be sent. The identification of the appropriate functional blocks may take place in a number of ways. In a preferred embodiment, the identification is accomplished through the use of a look-up table comprising a list of appropriate destinations keyed to information extracted from requests received from access points 102.
  • a secure support client server 104 is not used, and the functionality of access points 102 are suitably specified in order to obviate the need for server 104.
  • the functions of server 104 may be allocated and distributed throughout the DSS components in any advantageous manner.
  • transaction refers, generally, to any message communicated over the system for effecting a particular goal, for example, debit/charge authorization, preference changes, reservation requests, ticket requests, and the like.
  • FIG. 11 shows an exemplary transaction data structure useful in the context of performing an on-line transaction with a travel partner, wherein the field name 1102, data type 1104 ('C' for character), maximum byte-length 1106, and description 1108 are listed in tabular form.
  • the transaction messages suitably comprise comma delimited data packets, although other data structures may be employed.
  • CODUS 106 suitably securely stores information related to the state of the various issued smartcards 120.
  • CODUS 106 comprises a security engine 602, a data management module 604, a card object database 116, a card object administration module 606, and an audit file 608.
  • Security engine 602 provides suitable security for, inter alia, the information stored within card object database 116.
  • security engine 602 may utilize various authentication, data encryption, and digital signature techniques in connection with incoming and outgoing message packets.
  • Suitable algorithms in the context of the present invention include, for example, DES encryption, RSA authentication, and a variety of other symmetrical and non-symmetrical cryptographic techniques.
  • Data management module 604 suitably acts as a data interface between CODUS 106 and account maintenance 142 as well as between CODUS 106 and the various EDCUs 112. More specifically, module 604 converts and translates between the data format used in these systems. For example, data stored within object database 106 may not be stored in a format which can be easily used by EDCUs 112 or account maintenance 142. Accordingly, data management module 604 comprises suitable routines for effecting conversion and formatting of both incoming and outgoing data.
  • Card object administration module 606 preferably provides suitable database software to edit, update, delete, synchronize, and ensure non-corruption of data stored within object database 106.
  • database packages are suitable for this task, including, for example, various conventional fourth-generation relational database management systems (4GL RDBMS).
  • Audit file 608 suitably tracks changes to object database 116, thereby helping to ensure the integrity of card data stored within CODUS 106. More particularly, when changes to object database 116 take place as a result of preference updates, transactions, application structure changes, and the like, audit file 608 tracks suitable information related to these changes, e.g., time, date, and nature and content of the change.
  • Card object database 116 which may comprise a single database or a set of distributed databases, is used to store the known state of the various smartcards 120.
  • the state of a smartcard is characterized by a suitable set of card indicia.
  • card object database 116 stores information related to the individual applications present on the various smartcards 120 (i.e., the overall file structure) as well as the individual fields, directories, and data that comprise those applications.
  • a file structure for card object database 116 is chosen such that it includes a suitable set of data fields for a given smartcard 120.
  • EDSI 108 track changes to smartcard data and/or applications corresponding to individual enterprises.
  • EDSI 108 comprises a communication server 302, a security engine 304, and a customer database 306.
  • Communication server 302 suitably facilitates communication with enterprise networks 114 and update logic system 110.
  • server 302 is configured to translate between various formats, media, and communication protocols as may be necessary given the particular choice of components employed.
  • Security engine 304 provides suitable security measures with respect to the access and storage of information with customer database 306.
  • Security engine 304 may utilize various authentication, data encryption, and digital signature techniques in connection with incoming and outgoing message packets. Suitable algorithms in the context of the present invention, include, for example, DES encryption, RSA authentication, and a variety of other symmetrical and non-symmetrical cryptographic techniques.
  • Customer database 306 suitably provides a means for storing smartcard information related to individual partners or enterprises. That is, a particular enterprise (hosting, for example, enterprise network 114(a)) might compile, or employ others to compile, smartcard information related only to that enterprise. For example, a hotel chain might store loyalty, preference, and other data that relates specifically to that hotel chain. During synchronization (as described in further detail below) any changes to database 306 would be propagated through the system and, visa-versa, changes elsewhere in the system would be communicated to database 306. This communication is preferably done securely (using security engine 304) in conjunction with communication server 302.
  • the functionality provided by the EDSIs 108 are folded into the corresponding EDCU 112. That is, while an illustrated embodiment employs one or more physically separate EDSIs 108, it may be advantageous to further streamline the DSS by incorporate this functionality into the corresponding EDCU 112 functional block.
  • update logic system 110 formats and securely routes card data received from and transmitted to EDCUs 112 and EDSIs 108.
  • update logic system 110 includes a logic engine 402, a data management module 404, a security engine 406, an enterprise update administrator 408, and an enterprise update audit module 410.
  • Logic engine 402 suitably functions to direct and distribute information changes across the system.
  • logic engine 402 is able to determine which modules (i.e., which EDCUs 112 and EDSIs 108) need to reflect the change
  • Data management module 404 suitable acts as a data interface between EDSIs 108 and EDCUs 112. More specifically, module 404 is able to convert and translate between data format used in these systems. Accordingly, data management module 604 comprises suitable routines for effecting conversion and formatting of both incoming and outgoing data.
  • Security engine 406 is used to provide suitable security measures with respect to data flowing through update logic system 110.
  • Security engine 406 may utilize various authentication, data encryption, and digital signature techniques in connection with incoming and outgoing message packets.
  • Suitable algorithms in the context of the present invention include, for example, DES encryption, RSA authentication, and a variety of other symmetrical and non-symmetrical cryptographic techniques.
  • Enterprise update administrator 408 suitably comprises overhead software necessary to maintain data transfer between EDSIs 108 and EDCUs 112.
  • Enterprise update audit module 410 suitably tracks update information flowing through update logic system 110. More particularly, when information is communicated across update logic system 110, (as a result of preference updates, transactions, application structure changes, and the like), audit module 410 tracks suitable indicia of this information, e.g., time, date, and nature and content of the communication.
  • EDCUs 112 preferably store and coordinate the transfer of synchronization data corresponding to a particular enterprise.
  • enterprise data collection unit 112 includes a security engine 508, a customer update transaction database 504, a customer loyalty transaction database 510, a customer pending transaction database 514, an update database 502, an EDCU audit file 506, an EDCU administrative file 512, and an EDCU data management module 516.
  • Security engine 508 is used to provide suitable security measures with respect to data flowing through EDCU 112. Toward this end, security engine 406 may utilize various authentication, data encryption, and digital signature techniques in connection with incoming and outgoing message packets. Suitable algorithms in the context of the present invention, include, for example, DES encryption, RSA authentication, and a variety of other symmetrical and non-symmetrical conventional cryptographic techniques.
  • Customer update transaction database 504 is used to store information which has been updated on a smartcard 120, but which has not yet propagated to the various databases and networks that require updating.
  • a smartcard 120 may be used to change cardholder preferences in the course of a transaction with a particular enterprise. This information would, in the short term, be stored in database 504 (for the particular enterprise) until it could be fanned-out to CODUS 106 and the appropriate EDCUs 112 and EDSIs 108. This type of transaction is described in further detail below.
  • Customer loyalty transaction database 510 is suitably used to store loyalty information (e.g., frequent flier, frequent stayer, etc.) associated with a particular enterprise or partner.
  • loyalty transaction database 510 is not employed -- rather, the functionality of database 510 is incorporated into databases 502, 510, and 514 such that a loyalty transaction becomes just another transaction modality to be tracked by EDCU 112.
  • Customer pending transaction database 514 is suitably used to store information related to transactions which have taken place without direct use of the smartcard 120. More particularly, some transactions, such as preference changes and the like, may be initiated by a cardholder through a channel which does not involve use of the card, for example, through a verbal request over a standard telephone. In such a case, and as detailed further below, this data is suitably stored in pending transaction database 514. The transaction data remains in database 514 until the corresponding smartcard 120 is used in conjunction with an access point 120, whereupon smartcard 120 itself (as well as CODUS 106) is updated with this new information.
  • Update database 502 is suitably used to store other types of transactions, i.e., transactions which may not be classifiable as update, loyalty or pending.
  • update database 502 may be employed to store file structure updates as detailed below.
  • Audit file 506 is used to track changes to update database 504, pending database 514, database 502, and, in an illustrated embodiment, loyalty database 510. In an alternate embodiment, wherein no separate loyalty database 510 is used, audit file 506 tracks changes to databases 504, 514, and 502. Audit file 506 therefore helps to ensure the integrity of data in the respective files.
  • Administrative file 512 provides suitable database software necessary to edit, update, delete, synchronize, and ensure non-corruption of data stored within the various databases that comprise EDCU 112 -- i.e., databases 502, 504, 510, and 514.
  • Data management module 516 provides data management capabilities to facilitate data transfer between smartcards 120 and databases 504, 514, 502, and 510 as well as between these databases and the other systems -- i.e., update logic system 110 and CODUS 106. Thus, data management module 516 acts as interface to ensure seamless transfer of data between the various systems.
  • a suitable data communication network may consist of various physical connections using a variety of conventional data protocols, for example, the TCP/IP protocol. It will be appreciated that the individual connections between components of the present system may differ. For example, a wireless PCS network may be employed from an access point 102 to secure support client server 104, while a Internet TCP/IP connection may be employed from CODUS 106 to the various EDCUs 112.
  • a variety of hardware systems are suitable for implementing the present invention.
  • Various modems, routers, CPU's, monitors, back-up systems, power-supplies, and peripherals may be employed to realize the benefits of the present system.
  • a Compaq Prolinea computer operating in an OS/2 environment using IBM MQ Server software is used to implement secure support client server 104, wherein the various access points comprise stand-alone smartcard kiosks, an EDCU 112 and CODUS 116 is then implemented on a Compaq Prolinea computer operating in a Windows/NT environment running a suitable database software package.
  • personalization system 140 suitably comprises a card management system 902, a legacy management system 904, a gather application module 906, one or more databases 910, an activation block 908, a common card personalization utility 912 (CCP), a service bureau 914, a common card security server 916, a key management system 918, and one or more key systems 920.
  • Key management system 918 suitably comprises a database module 922, CID replace module 924, key system 926, and key system 928.
  • CCP 912 suitably communicates with CODUS 106 (shown in FIG. 1), and legacy management system 904 suitably communicates with account maintenance 142 which is also configured to communicate with CODUS 106.
  • Card management system 902 suitably receives the card request 901 and initiates the gathering of information from various sources.
  • card request 901 consists of various request information intended to specify a desired group of card characteristics. Such characteristics might include, for example: a list of desired applications (airline, hotel, rental car, etc.); a designation of whether the card is new, a renewal, or a replacement; a list of default cardmember preferences corresponding to the desired applications; personal information related to the cardmember (name, address, etc.); and required security levels.
  • Card management system 902 suitably parses the card request and, for information already stored by the issuer, sends a request to legacy card management system 904. For information not available as legacy data, card management system 902 forwards the relevant components of card request 901 to gather application module 906.
  • card management system 902 chooses the optimum smartcard physical characteristics for a particular card request 901. That is, card management system 902 suitably determines the appropriate type of smartcard chip to be used based on a number of factors, for example, memory requirements and computational complexity of the desired security functions. Similarly, the optimum smartcard operating system (SCOS) may be chosen. In an alternate embodiment, the smartcard chip, operating system, and the like, are specified in card request 901.
  • SCS smartcard operating system
  • Legacy management system 904 acts as a suitable repository of information related to the cardholder's past relationship -- if any -- with the card issuing organization. For example, a cardholder might have a long-standing credit or debit account with issuing organization (based on a standard embossed mag-stripe card) and this information might be advantageously incorporated into the issued card.
  • Gather application module 906 is suitably configured to receive information from card management system 902 and legacy management system 904 and then interface with the various databases 910 to gather all remaining application information specified in card request 901.
  • databases 910 correspond to and are associated with the individual partnering enterprises which offer smartcard applications for use in smartcard 120 (e.g., enterprise networks 114 in FIG. 1).
  • a card request 901 which included a request for a hotel application would trigger gather application 906 to initiate data communication with the appropriate hotel database 910.
  • Hotel database 910 would then return information specifying the correct file structure, access conditions (security), default values, and other data necessary to configure smartcard 120 with the requested application.
  • Communication with the various databases 910 may take place through any suitable means, for example, data communication over the Internet, PSTN, and the like, or through other channels, such as simple phone requests.
  • Activation block 908 is suitably used to provide a means for the cardmember to activate the card once it has been issued. For example, it is common for credit cards and the like to be sent to the cardmember unactivated, requiring that the cardmember call (or otherwise contact) an automated system at the issuer in order to activate the card. This is typically accomplished via entry of the card number and other suitable ID using a touch-tone phone. In this regard, activation block 908 is used to facilitate this function for the requested smartcard, i.e., to specify whether such activation is necessary for a particular card.
  • CCP 912 is used to create a correctly formatted card "object" -- i.e., the operating system, file structure and all other available card data to be downloaded to card 120 -- then transfer this information to service bureau 914 (for creation of the smartcard) and CODUS 106 (for recording the card's state as issued).
  • CCP 912 is preferably configured to tailor the format of the card object to the specific card issuance system to be used (described below). Thus, gather application system 906 can deliver a relatively high-level functionality request, and CCP 912 can create the specific "object" to be used in the implementation.
  • Personalization Service Bureau 914 comprises suitable hardware and software components to complete production of the smartcards for issuance to the respective cardmembers.
  • service bureau 914 includes a suitable smartcard "printer” to handle the transfer of information to the smartcard chip as well as any conventional embossing or mag-stripe writing that may take place.
  • smartcard printers include, for example, any of the series 9000 and series 150i smartcard issuance systems manufactured by Datacard Corporation of Minnetonka, MN.
  • Common card security server 916 suitably comprises software and hardware components necessary to retrieve cryptographic key information from various enterprise key systems 920.
  • this information is accessed by service bureau 914 in order to complete the personalization process. More particularly, it will typically be the case that a smartcard 120 contains a number of different applications associated with a wide range of enterprise organizations.
  • a set of access condition rules are suitably implemented using cryptographic keys which are known by the appropriate parties.
  • service bureau 914 -- whose task it is to create and populate the card file structure -- will not, ab initio , have access to the keys necessary to perform this function.
  • CCSS 916 is suitably used to facilitate this process by receiving information from CCP 912 regarding the identity of the various applications to be created in the various cards, then, when prompted by service bureau 914 (or, alternatively, prior to issuance by service bureau 914), contacting the appropriate key system 920 to request a key to be transmitted to service bureau 914 during personalization.
  • Key systems 920 comprise suitable database systems capable of storing, generating, and securely transmitting cryptographic keys associated with a particular enterprise.
  • Key management system 918 is, in this context, a system comparable to key systems 920, but which is "owned” by the party implementing the personalization system.
  • the key-generating function may be distributed between CCSS and key systems 920. That is, the keys may be generated in real time at CCSS 916 (in accordance with algorithms and key information received from the particular enterprises), rather than being generated at key systems 920.
  • FIG. 9 may be implemented using a variety of hardware and software components, both off-the-shelf and/or custom-developed.
  • Database-intensive functions performed, for example, by card management system 902 may be implemented using any suitable database package, e.g., Codebase, dBase, or the like.
  • a personalization system as described above in conjunction with FIG. 9 is suitably used to efficiently issue a large number of smartcards with a wide range of functionality levels.
  • This task involves obtaining and coordinating, in a timely fashion, accurate data for individual cardmembers across the various partnering enterprises supported by the system.
  • certain partnering enterprises desire to limit the dissemination of proprietary data.
  • This data might include, for example, private keys used in connection with smartcard access conditions as well as file structure and cardmember personal data.
  • Step 1002 the system receives a smartcard request.
  • card management system 902 is suitably used to receive the card request and initiate the gathering of information from various sources.
  • Card request 901 suitably consists of request information intended to specify a desired group of card characteristics. Such characteristics might include, for example: a list of desired applications (airline, hotel, rental car, etc.); a designation of whether the card is new, a renewal, or a replacement; a list of default cardmember preferences corresponding to the desired applications; personal information related to the cardmember (name, address, etc.); and required security levels.
  • Step 1004 the system selects the smartcard type and configuration appropriate for the given card request 901.
  • This step is suitably performed by card management system 902.
  • card management system 902 examines a number of factors in light of information received in card request 901 (e.g., memory requirements, desired security functions, and the like), then selects an appropriate smartcard chip from a library of available chips. In the same way, the optimum smartcard operating system (SCOS) may also be selected.
  • a number of factors in light of information received in card request 901 e.g., memory requirements, desired security functions, and the like
  • the optimum smartcard operating system may also be selected.
  • cardmember information is obtained. This step is suitably performed by gather application module 906 operating in conjunction with databases 910 and legacy management system 904. More particularly, cardmember-specific information is preferably classified in two groups: information known to the personalization system, and information not known by the personalization system. Known information generally consists of data acquired through a past relationship with the organization hosting the personalization system. In such a case, certain data such as cardholder name, preferred billing address, title, company, etc., will most likely already be known, as will certain application data. Such information is suitably stored in, and may be retrieved from, one or more databases comprising legacy management system 904. As part of Step 1006, the system (specifically, module 908) preferably determines whether the card should require activation.
  • Activation typically involves the use of an automated phone system).
  • the choice of whether a particular card requires activation may be based on a number of factors, for example, demographics, crime-rate numbers, or mail fraud statistics associated with the cardmember's zip-code number.
  • gather application module 906 suitably communicates with databases 910 to retrieve the information needed to satisfy card request 901.
  • This information will typically consist of file structure information, e.g., the DF and EF hierarchy, data types and lengths, and access condition specifications for the particular enterprise-sponsored application.
  • gather application module 906 would contact the database corresponding to the enterprise hosting the airline application, then download all necessary file structure information. This process would continue in turn for each new or modified application to be incorporated into the smartcard.
  • Step 1008 a full cardmember data set is created, suitably using CCP 912.
  • This data set, or "card object” will ultimately be used by service bureau 914 to create the physical smartcard.
  • the form of the card object may vary.
  • the card object comprises what has been termed a Binary Large Object ("BLOB").
  • BLOB Binary Large Object
  • the card object is preferably tailored to the selected smartcard configuration (e.g., chip type and operating system as specified in Step 1004), the content of cardmember information data (gathered in Step 1006), and the intended smartcard “printer” (i.e., the apparatus used to create the finished card within service bureau 914).
  • step 1008 the system need only develop a relatively high-level model of the intended smartcard data structure; the specifics are substantially invisible to all but CCP 912.
  • various details of the smartcard data object may be determined at a prior point in the system. That is, the functionality of CCP 912 may be distributed among various components of the system.
  • Step 1010 This data is then sent to CODUS 106 (Step 1010). This ensures that the DSS (particularly CODUS 106) has a record of the smartcard state at the time of personalization. This information is then immediately available to account maintenance system 142.
  • Step 1014 the necessary keys are acquired to allow service bureau 914 to create the finished smartcard.
  • Step 1014 is suitably performed by CCSS 916 concurrently or serially with the issuance process.
  • service bureau 914 interrogates CCSS 916 for the appropriate cryptographic keys. These keys have either been retrieved from key systems 920 and 918 earlier (i.e., after Step 1012), or are retrieved in real-time in response to the request from service bureau 914.
  • the keys may be retrieved by CCSS 916 and transmitted to CCP 912 prior to transmission of the card object to service bureau 914. In either case, the key or keys are then retrieved for inclusion in the card object created in Step 1008.
  • Step 1016 the actual card is issued.
  • Service bureau 914 suitably downloads the card object into the correct smartcard hardware using the correct cryptographic keys.
  • the initialized smartcard may then be packaged and distributed to the appropriate cardmember in accordance with conventional methods.
  • a dynamic synchronization system as described above in various embodiments is used to track the "state" of the consumer's smartcard.
  • the state of the smartcard is suitably characterized by the structure of applications used in the smartcard and the various pieces of data that are stored within these applications.
  • data files and directories may be stored in a "tree" structure in smartcard 120. That is, the smartcard file structure suitably resembles the well known MS-DOS (Microsoft Disk Operating System) file structure wherein files are logically organized within a hierarchy of directories.
  • MS-DOS Microsoft Disk Operating System
  • three types of files are defined in ISO 7816-4: dedicated files (DF), elementary files (EF), and a master file (MF).
  • the master file is analogous to the MS-DOS "root" directory, and contains all other files and directories.
  • Dedicated files are actually directories or "folders" for holding other DFs or EFs.
  • the MF may contain an arbitrary number of DFs, and these DFs may or may not contain other DFs.
  • Elementary files are used to store user data, and may exist within a dedicated file, or within the master file.
  • Higher level DFs i.e., DFs which house particular applications
  • ADFs application dedicated files
  • the scope of the present invention is not, however, limited to this type of multi-function card.
  • Other implementations, for example, Multos or Java-based cards, are also suitable within the context of the instant invention.
  • the cardholder suitably inserts card 120 into a conveniently located access point 102, whereupon authentication of the card and/or card-reader takes place (Step 802).
  • authentication takes place in accordance with relevant sections of the ISO 7816 standard.
  • the cardholder uses a suitable user interface (supplied by the access point 102 working in conjunction with server 104) in order to perform a transaction -- i.e., to request a change to the preferences file (Step 804).
  • This change would typically be reflected at the smartcard 120 immediately. That is, the access point 102 and/or server 104 would include the functionality necessary to access and update the appropriate files within smartcard 120.
  • Communication router 206 in server 104 then routes the transaction to the appropriate party, i.e., an EDSI 108 or an EDCU 112, corresponding to branches 807 and 812 respectively. That is, depending on the system configuration, the file to be changed might be associated with a particular enterprise or, alternatively, might be associated with the organization hosting the DSS. These two cases are described in turn.
  • update logic system 110 transfers this change request to the appropriate EDCU 112 -- i.e., the EDCU 112 corresponding to the particular EDSI (Step 810).
  • This information is suitably stored in the corresponding update database 504.
  • the information is also distributed to other EDSIs.
  • update logic system 110 would identify those systems that would benefit from knowing the cardholder's smoking status. Such systems might include, for example, various hotels, rental car agencies, and the like.
  • the data may first be stored at the appropriate EDCU (Step 812), then distributed to other EDUCs 112 and EDSIs 108 as described above.
  • the card data change is then transferred to CODUS 106. Specifically, the various fields and files associated with the smartcard 120 are updated to reflect the change stored in update database 504. Thus, the information within CODUS 106 conforms to that contained within smartcard 120 and the various EDCUs 112 and EDSIs 108. After this transfer, the corresponding change data in update database 504 is cleared (Step 818).
  • the cardholder might make a change or perform a transaction through a channel that does not directly involve smartcard 120, thus creating an inconsistency between the data in smartcard 120 and the data in various databases throughout the DSS.
  • a case might arise, for example, when the cardholder calls a hotel to make a reservation (rather than performing the transaction on line using smartcard 120) and makes an oral request to change his preferences from smoking to non-smoking.
  • the cardholder first contacts an enterprise through a means that does not include smartcard 120 -- i.e., a "smartcard not present" transaction (Step 702). Using an appropriate interface (voice, keypad, etc.), a change or transaction is selected (Step 704). This change is then stored locally within a particular enterprise network 114 and/or is stored within an EDSI 108 (Step 706).
  • Step 708 update logic system 110 routes this information to the corresponding EDCU 112, where it resides in pending database 514.
  • smartcard 120 itself is oblivious to the change.
  • the corresponding enterprise would likely look first to the data structure in smartcard 120 for preferences, and as just stated, would most likely arrive at the wrong conclusion (e.g., a smoking room might be assigned notwithstanding the cardholder's expressed preference).
  • Steps 710-712 a method by which the smartcard is updated upon its next use. That is, after the smartcard is inserted at an access point 102 and is suitably authenticated (Step 710), the system interrogates pending database 514 to determine whether any changes have been made. If so, the appropriate information is downloaded to smartcard 120 (Step 712).
  • changes to the structure of data stored in smartcard 120 might also be desirable in certain contexts. That is, during the life of a smartcard, it is likely that the card issuer, a partnering enterprise, or the cardholder himself may desire to extend the card's functionality by augmenting the suite of applications housed within the card. For example, a cardholder who uses a smartcard for rental car and airline reservations might also wish to use the card for acquiring and paying for hotel reservations. In such a case, the appropriate hotel partner may process the cardholder's request and arrange for addition of a hotel application to be added to the smartcard file structure. In another example, the smartcard issuer might authorize the addition of a new application on its own, for example, a credit and/or debit application. Conversely, it may also be appropriate in some instances to remove applications from the card.
  • the types of file structure changes described above can be handled in a manner analogous to the procedure set forth in FIG. 7, depending, to some extent, upon which party originates the file structure change. That is, as in Step 712, the appropriate file structure change information may be stored in EDCU 112 (for example, in database 502), and then transferred to smartcard 120 when the card is used in conjunction with an on-line transaction (Steps 710 and 712). After the file structure on smartcard 120 is augmented or otherwise modified, CODUS 106 (specifically, database 116) is similarly modified to reflect the change. The change information is then cleared from database 502 (Step 716).

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Computer Security & Cryptography (AREA)
  • Storage Device Security (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Sub-Exchange Stations And Push- Button Telephones (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Credit Cards Or The Like (AREA)
  • Optical Couplings Of Light Guides (AREA)
  • Table Devices Or Equipment (AREA)
  • Heat Treatment Of Steel (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Claims (9)

  1. Système à carte à puce intégrée pour la gestion de la personnalisation et de la synchronisation d'une carte à puce, dans lequel ladite carte à puce comprend un objet de carte ayant au moins une application, ledit système comprenant :
    un serveur de sécurité (104) ;
    au moins un système de clé (920) associé à ladite au moins une application, ledit système de clé étant configuré pour communiquer avec ledit serveur de sécurité et pour fournir une clé en réponse à une demande émanant dudit serveur de sécurité ;
    un utilitaire de personnalisation (140) configuré pour recevoir ledit objet de carte et pour communiquer avec ledit serveur de sécurité ;
    ledit utilitaire de personnalisation étant configuré, en outre, pour ajouter ladite clé audit objet de carte ;
    un système de mise à jour de base de données d'objets de carte (106) configuré pour communiquer avec ledit utilitaire de personnalisation et pour mémoriser ledit objet de carte associé à ladite carte à puce ;
    une unité de collecte de données d'entreprise (112) configurée pour stocker des transactions mises à jour et des transactions en cours, associées à ladite carte à puce, ladite unité de collecte de données d'entreprise étant configurée pour communiquer avec ledit système de mise à jour de base de données d'objets de carte ;
    au moins un point d'accès (102) configuré pour former une interface avec ladite carte à puce et ladite unité de collecte de données d'entreprise.
  2. Système selon la revendication 1, comprenant, en outre, un système de gestion de carte (902), ledit système de gestion de carte étant configuré pour recevoir une demande de carte (901) et pour communiquer ladite demande de carte audit utilitaire de personnalisation.
  3. Système selon la revendication 2, comprenant, en outre, un module d'application de regroupement (906) configuré pour communiquer avec ledit système de gestion de carte et regrouper des informations d'application en provenance d'au moins une base de données, en conformité avec ladite demande de carte.
  4. Système selon la revendication 1, comprenant, en outre, un service bureau (914) configuré pour communiquer avec ledit utilitaire de personnalisation et ledit serveur de sécurité afin de produire la carte à puce.
  5. Système selon la revendication 1, comportant, en outre, un bloc d'activation configuré pour déterminer si la carte à puce aura besoin ou non d'être activée par un détenteur de la carte.
  6. Système selon la revendication 3, comprenant, en outre, un système de gestion patrimonial (904), ledit système de gestion patrimonial étant configuré pour communiquer avec ledit système de gestion de carte et pour transmettre des données patrimoniales audit module d'application de regroupement agissant en réponse à ladite demande de carte.
  7. Système selon la revendication 1, comprenant, en outre, un système de mise à jour de base de données d'objets de carte (606) configuré pour communiquer avec ledit utilitaire de personnalisation et pour mémoriser ledit objet de carte associé à ladite carte à puce.
  8. Système selon la revendication 1, comprenant, en outre, un système logique de mise à jour (110) couplé à au moins une interface de synchronisation de données d'entreprise (108), ledit système logique de mise à jour (110) étant configuré pour acheminer des informations de carte, de manière sûre, entre ladite interface de synchronisation de données d'entreprise (108) et lesdites unités de collecte de données d'entreprise (112), ladite interface de synchronisation de données d'entreprise (108) étant couplée à un réseau d'entreprise (114) configuré pour communiquer avec ledit point d'accès.
  9. Système selon la revendication 8, comprenant, en outre, un serveur client d'assistance sécurisée configuré pour communiquer avec ledit point d'accès, ledit serveur client d'assistance sécurisée étant, en outre, configuré pour fournir des fonctionnalités de communication, de manière adaptative, conformément aux fonctionnalités de communication disponibles audit point d'accès.
EP99920324A 1998-05-06 1999-05-04 Procede et appareil de personnalisation et de synchronisation dynamique de carte a puce Expired - Lifetime EP1076875B1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US09/073,618 US6199762B1 (en) 1998-05-06 1998-05-06 Methods and apparatus for dynamic smartcard synchronization and personalization
US73618 1998-05-06
PCT/US1999/009731 WO1999057675A1 (fr) 1998-05-06 1999-05-04 Procede et appareil de personnalisation et de synchronisation dynamique de carte a puce

Publications (3)

Publication Number Publication Date
EP1076875A1 EP1076875A1 (fr) 2001-02-21
EP1076875A4 EP1076875A4 (fr) 2003-03-12
EP1076875B1 true EP1076875B1 (fr) 2004-04-07

Family

ID=22114781

Family Applications (1)

Application Number Title Priority Date Filing Date
EP99920324A Expired - Lifetime EP1076875B1 (fr) 1998-05-06 1999-05-04 Procede et appareil de personnalisation et de synchronisation dynamique de carte a puce

Country Status (14)

Country Link
US (1) US6199762B1 (fr)
EP (1) EP1076875B1 (fr)
JP (1) JP4170590B2 (fr)
CN (1) CN1308750A (fr)
AT (1) ATE263992T1 (fr)
AU (1) AU762962B2 (fr)
BR (1) BR9910222A (fr)
CA (1) CA2330625C (fr)
DE (1) DE69916260T2 (fr)
ES (1) ES2221379T3 (fr)
HK (1) HK1033191A1 (fr)
NZ (1) NZ508577A (fr)
TW (1) TW522350B (fr)
WO (1) WO1999057675A1 (fr)

Families Citing this family (236)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
NZ501859A (en) * 1997-06-16 2002-08-28 Swisscom Mobile Ag A mobile device including a removable chip card with an independent power source
US7364068B1 (en) 1998-03-11 2008-04-29 West Corporation Methods and apparatus for intelligent selection of goods and services offered to conferees
US6055513A (en) 1998-03-11 2000-04-25 Telebuyer, Llc Methods and apparatus for intelligent selection of goods and services in telephonic and electronic commerce
US7437313B1 (en) 1998-03-11 2008-10-14 West Direct, Llc Methods, computer-readable media, and apparatus for offering users a plurality of scenarios under which to conduct at least one primary transaction
US8315909B1 (en) 1998-03-11 2012-11-20 West Corporation Methods and apparatus for intelligent selection of goods and services in point-of-sale commerce
US7386485B1 (en) 2004-06-25 2008-06-10 West Corporation Method and system for providing offers in real time to prospective customers
US7729945B1 (en) 1998-03-11 2010-06-01 West Corporation Systems and methods that use geographic data to intelligently select goods and services to offer in telephonic and electronic commerce
US6131811A (en) 1998-05-29 2000-10-17 E-Micro Corporation Wallet consolidator
US6808111B2 (en) * 1998-08-06 2004-10-26 Visa International Service Association Terminal software architecture for use with smart cards
US6032136A (en) * 1998-11-17 2000-02-29 First Usa Bank, N.A. Customer activated multi-value (CAM) card
TW463107B (en) * 1998-12-22 2001-11-11 Ibm Extended card file system
US6912580B1 (en) * 1999-01-27 2005-06-28 International Business Machines Corporation Virtual shadow briefcase in servers supporting moving embedded clients
JP3545627B2 (ja) * 1999-02-08 2004-07-21 株式会社東芝 携帯可能電子装置
US6430599B1 (en) * 1999-06-15 2002-08-06 Sun Microsystems, Inc. Just-in-time services for small footprint devices
US7889052B2 (en) 2001-07-10 2011-02-15 Xatra Fund Mx, Llc Authorizing payment subsequent to RF transactions
US6588673B1 (en) * 2000-02-08 2003-07-08 Mist Inc. Method and system providing in-line pre-production data preparation and personalization solutions for smart cards
DE10015732A1 (de) * 2000-03-29 2001-10-11 Skidata Ag Zugangsberechtigungs-Buchungsverfahren
US6957776B1 (en) * 2000-03-30 2005-10-25 Qwest Communications International Inc. System and method for managing a plurality of local lists of a single user
US6981028B1 (en) 2000-04-28 2005-12-27 Obongo, Inc. Method and system of implementing recorded data for automating internet interactions
US6755341B1 (en) 2000-05-15 2004-06-29 Jacob Y. Wong Method for storing data in payment card transaction
US6609654B1 (en) 2000-05-15 2003-08-26 Privasys, Inc. Method for allowing a user to customize use of a payment card that generates a different payment card number for multiple transactions
US6805288B2 (en) 2000-05-15 2004-10-19 Larry Routhenstein Method for generating customer secure card numbers subject to use restrictions by an electronic card
US6592044B1 (en) 2000-05-15 2003-07-15 Jacob Y. Wong Anonymous electronic card for generating personal coupons useful in commercial and security transactions
US20020091562A1 (en) * 2000-06-02 2002-07-11 Sony Corporation And Sony Electrics Inc. Facilitating offline and online sales
US20040025053A1 (en) * 2000-08-09 2004-02-05 Hayward Philip John Personal data device and protection system and method for storing and protecting personal data
CA2324772A1 (fr) * 2000-10-30 2002-04-30 Ivi Checkmate Corp. Systeme de securite pour l'echange d'information cryptee
JP3636984B2 (ja) * 2000-11-09 2005-04-06 株式会社日立製作所 Ｉｃカードシステム用記録媒体及びｉｃカードシステム
SE0100474D0 (sv) * 2001-02-14 2001-02-14 Ericsson Telefon Ab L M A security architecture
GB2373880A (en) * 2001-03-24 2002-10-02 Hewlett Packard Co Method and apparatus for configuring a portable computing device
US7613834B1 (en) * 2001-04-04 2009-11-03 Palmsource Inc. One-to-many device synchronization using downloaded/shared client software
US20030149576A1 (en) * 2001-04-19 2003-08-07 Sunyich Steven L. Personalized smart room
US7739162B1 (en) 2001-05-04 2010-06-15 West Corporation System, method, and business method for setting micropayment transaction to a pre-paid instrument
JP3557181B2 (ja) * 2001-05-14 2004-08-25 株式会社東芝 Ｉｃカード発行システム
US7725427B2 (en) 2001-05-25 2010-05-25 Fred Bishop Recurrent billing maintenance with radio frequency payment devices
US8001054B1 (en) 2001-07-10 2011-08-16 American Express Travel Related Services Company, Inc. System and method for generating an unpredictable number using a seeded algorithm
US7360689B2 (en) 2001-07-10 2008-04-22 American Express Travel Related Services Company, Inc. Method and system for proffering multiple biometrics for use with a FOB
US20040236699A1 (en) 2001-07-10 2004-11-25 American Express Travel Related Services Company, Inc. Method and system for hand geometry recognition biometrics on a fob
US8294552B2 (en) 2001-07-10 2012-10-23 Xatra Fund Mx, Llc Facial scan biometrics on a payment device
US8548927B2 (en) 2001-07-10 2013-10-01 Xatra Fund Mx, Llc Biometric registration for facilitating an RF transaction
US7303120B2 (en) 2001-07-10 2007-12-04 American Express Travel Related Services Company, Inc. System for biometric security using a FOB
US7735725B1 (en) 2001-07-10 2010-06-15 Fred Bishop Processing an RF transaction using a routing number
US7705732B2 (en) 2001-07-10 2010-04-27 Fred Bishop Authenticating an RF transaction using a transaction counter
US8279042B2 (en) 2001-07-10 2012-10-02 Xatra Fund Mx, Llc Iris scan biometrics on a payment device
US7762457B2 (en) 2001-07-10 2010-07-27 American Express Travel Related Services Company, Inc. System and method for dynamic fob synchronization and personalization
US9031880B2 (en) 2001-07-10 2015-05-12 Iii Holdings 1, Llc Systems and methods for non-traditional payment using biometric data
US7668750B2 (en) 2001-07-10 2010-02-23 David S Bonalle Securing RF transactions using a transactions counter
US7249112B2 (en) 2002-07-09 2007-07-24 American Express Travel Related Services Company, Inc. System and method for assigning a funding source for a radio frequency identification device
US9024719B1 (en) * 2001-07-10 2015-05-05 Xatra Fund Mx, Llc RF transaction system and method for storing user personal data
US9454752B2 (en) 2001-07-10 2016-09-27 Chartoleaux Kg Limited Liability Company Reload protocol at a transaction processing entity
US20030018892A1 (en) * 2001-07-19 2003-01-23 Jose Tello Computer with a modified north bridge, security engine and smart card having a secure boot capability and method for secure booting a computer
US20080120147A1 (en) * 2001-07-20 2008-05-22 Rodger Burrows Methods and apparatus for electronically storing travel agents coupons
US6993772B2 (en) 2001-09-18 2006-01-31 The Mathworks, Inc. Common communication system for control instruments
GB0125222D0 (en) * 2001-10-19 2001-12-12 Barts & London Nhs Trust Composition for the treatment of microbial infections
US7243853B1 (en) 2001-12-04 2007-07-17 Visa U.S.A. Inc. Method and system for facilitating memory and application management on a secured token
US7134087B2 (en) * 2002-04-05 2006-11-07 Maritz Inc. System and method for transacting purchases with a cash vendor using points
US6726107B1 (en) * 2002-04-12 2004-04-27 Tracfone Wireless, Inc. Method and system for activating a roadside assistance membership
US8396809B1 (en) 2002-05-14 2013-03-12 Hewlett-Packard Development Company, L.P. Method for reducing purchase time
US7356516B2 (en) * 2002-06-13 2008-04-08 Visa U.S.A. Inc. Method and system for facilitating electronic dispute resolution
US6805287B2 (en) 2002-09-12 2004-10-19 American Express Travel Related Services Company, Inc. System and method for converting a stored value card to a credit card
US6837425B2 (en) 2002-09-13 2005-01-04 Visa U.S.A. Inc. Compact protocol and solution for substantially offline messaging between portable consumer device and based device
US20040139021A1 (en) * 2002-10-07 2004-07-15 Visa International Service Association Method and system for facilitating data access and management on a secure token
US20040088547A1 (en) * 2002-11-04 2004-05-06 Colnot Vincent Cedric Method and apparatus to secure online transactions over the phone
CN100498685C (zh) * 2002-12-23 2009-06-10 德克斯特拉公司 移动数据和软件更新系统及方法
US8306908B1 (en) 2002-12-31 2012-11-06 West Corporation Methods and apparatus for intelligent selection of goods and services in telephonic and electronic commerce
US8712857B1 (en) 2003-03-31 2014-04-29 Tuxis Technologies Llc Methods and apparatus for intelligent selection of goods and services in mobile commerce
US7342918B2 (en) * 2003-04-15 2008-03-11 American Express Travel Related Services Co., Inc. Transaction card information access web service
US20040236680A1 (en) * 2003-05-22 2004-11-25 International Business Machines Corporation Method and apparatus for displaying embedded chip states and embedded chip end-user application states
US9959544B2 (en) * 2003-05-22 2018-05-01 International Business Machines Corporation Updating an application on a smart card and displaying an advertisement
US20050051620A1 (en) * 2003-09-04 2005-03-10 International Business Machines Corporation Personal data card processing system
US7287078B2 (en) * 2003-10-31 2007-10-23 Hewlett-Packard Development Company, L.P. Restoration of lost peer-to-peer offline transaction records
CH716409B1 (de) * 2003-11-12 2021-01-29 Legic Identsystems Ag Verfahren zum Einschreiben einer Datenorganisation in Identifikationsmedien und zum Einschreiben und Ausführen von Applikationen in der Datenorganisation.
US7440982B2 (en) * 2003-11-13 2008-10-21 Commvault Systems, Inc. System and method for stored data archive verification
FR2866772B1 (fr) * 2004-02-20 2006-04-28 Viaccess Sa Procede d'appariement d'un terminal recepteur avec une pluralite de cartes de controle d'acces
US7165727B2 (en) * 2004-02-24 2007-01-23 Sun Microsystems, Inc. Method and apparatus for installing an application onto a smart card
US7140549B2 (en) * 2004-02-24 2006-11-28 Sun Microsystems, Inc. Method and apparatus for selecting a desired application on a smart card
US7374099B2 (en) * 2004-02-24 2008-05-20 Sun Microsystems, Inc. Method and apparatus for processing an application identifier from a smart card
US7191288B2 (en) * 2004-02-24 2007-03-13 Sun Microsystems, Inc. Method and apparatus for providing an application on a smart card
US7314165B2 (en) * 2004-07-01 2008-01-01 American Express Travel Related Services Company, Inc. Method and system for smellprint recognition biometrics on a smartcard
US7341181B2 (en) * 2004-07-01 2008-03-11 American Express Travel Related Services Company, Inc. Method for biometric security using a smartcard
US7318550B2 (en) * 2004-07-01 2008-01-15 American Express Travel Related Services Company, Inc. Biometric safeguard method for use with a smartcard
US7325724B2 (en) 2004-07-01 2008-02-05 American Express Travel Related Services Company, Inc. Method for registering a biometric for use with a smartcard
US7314164B2 (en) * 2004-07-01 2008-01-01 American Express Travel Related Services Company, Inc. System for biometric security using a smartcard
US7363504B2 (en) 2004-07-01 2008-04-22 American Express Travel Related Services Company, Inc. Method and system for keystroke scan recognition biometrics on a smartcard
US7178720B1 (en) 2004-09-30 2007-02-20 West Corporation Methods, computer-readable media, and computer program product for intelligent selection of items encoded onto portable machine-playable entertainment media
US7232073B1 (en) 2004-12-21 2007-06-19 Sun Microsystems, Inc. Smart card with multiple applications
US20070200679A1 (en) * 2005-05-06 2007-08-30 Colby Steven M RFID Device Including Multiple RFID Tags
US9524458B2 (en) 2005-02-07 2016-12-20 Mynette Technologies, Inc. Switchable epassport including shielding
US20060267737A1 (en) * 2005-05-27 2006-11-30 Colby Steven M RF Powered Remote Control
US20070200684A1 (en) * 2005-05-06 2007-08-30 Colby Steven M RFID Device Configured for Data Entry
US20070200680A1 (en) * 2005-05-06 2007-08-30 Colby Steven M Transaction Card Including Switchable RFID Tag
US8816826B2 (en) * 2005-05-06 2014-08-26 Steven M. Colby Passive radio frequency data logger
US20070200681A1 (en) * 2005-05-06 2007-08-30 Colby Steven M Identity Device Including Switchable RFID Tag
US20070200682A1 (en) * 2005-05-06 2007-08-30 Colby Steven M RFID Device Including Multiple Active Modes
US9569777B2 (en) 2005-02-07 2017-02-14 Mynette Technologies, Inc. EPassport including shielding method
FR2882880B1 (fr) * 2005-03-04 2007-06-22 Barret Patrick Procede de securisation d'une transaction avec une carte de paiement, et centre d'autorisation pour la mise en oeuvre de ce procede
WO2007105120A1 (fr) * 2006-03-14 2007-09-20 Nxp B.V. Carte à puce configurable automatiquement et procédé de configuration d'une telle carte
CN100517236C (zh) 2006-04-03 2009-07-22 北京握奇数据系统有限公司 智能卡嵌入式操作系统及其控制方法
US7527208B2 (en) * 2006-12-04 2009-05-05 Visa U.S.A. Inc. Bank issued contactless payment card used in transit fare collection
US8118223B2 (en) 2006-09-28 2012-02-21 Visa U.S.A. Inc. Smart sign mobile transit fare payment
US8738485B2 (en) 2007-12-28 2014-05-27 Visa U.S.A. Inc. Contactless prepaid product for transit fare collection
US8346639B2 (en) 2007-02-28 2013-01-01 Visa U.S.A. Inc. Authentication of a data card using a transit verification value
US20080208681A1 (en) * 2006-09-28 2008-08-28 Ayman Hammad Payment using a mobile device
US8386349B2 (en) 2007-02-28 2013-02-26 Visa U.S.A. Inc. Verification of a portable consumer device in an offline environment
US20080203170A1 (en) * 2007-02-28 2008-08-28 Visa U.S.A. Inc. Fraud prevention for transit fare collection
US8523069B2 (en) 2006-09-28 2013-09-03 Visa U.S.A. Inc. Mobile transit fare payment
JP4304300B2 (ja) * 2006-11-01 2009-07-29 日本電気株式会社 ユーザ装置、サーバ、アップグレードサービスシステム、その方法およびプログラム
CN100535935C (zh) 2006-12-26 2009-09-02 北京握奇数据系统有限公司 Cpu与逻辑加密双用智能卡及其数据同步方法
US20080265020A1 (en) * 2007-02-09 2008-10-30 Business Intelligent Processing Systems Plc System and method for performing payment transactions, verifying age, verifying identity, and managing taxes
AU2009200139B2 (en) 2008-01-15 2012-02-16 Aristocrat Technologies Australia Pty Limited A method of processing a user data card, an interface module and a gaming system
US8831976B2 (en) * 2009-01-22 2014-09-09 Maritz Holdings Inc. System and method for transacting purchases with a cash vendor using points and a virtual credit card
US8401964B2 (en) * 2009-04-28 2013-03-19 Mastercard International Incorporated Apparatus, method, and computer program product for encoding enhanced issuer information in a card
US9523985B1 (en) 2009-08-11 2016-12-20 Rockwell Collins, Inc. Real time and in-flight dynamic personalization of an aircraft
CN102103651B (zh) * 2009-12-21 2012-11-14 中国移动通信集团公司 一种一卡通系统的实现方法和系统以及一种智能卡
GB2476987B (en) * 2010-01-19 2013-11-27 Haim Cohen Transaction card with improved security features
GB2480429A (en) * 2010-05-14 2011-11-23 Giesecke & Devrient Gb Ltd Personalising portable data carriers by use of a data preparation parameter
CN102088349B (zh) * 2010-12-27 2013-07-10 深圳市国民电子商务有限公司 一种智能卡个人化的方法及系统
US9191813B2 (en) 2010-12-30 2015-11-17 Mozido Corfire—Korea, Ltd. System and method for managing OTA provisioning applications through use of profiles and data preparation
US8538845B2 (en) 2011-06-03 2013-09-17 Mozido, Llc Monetary transaction system
WO2012170895A1 (fr) * 2011-06-09 2012-12-13 Yeager C Douglas Systèmes et procédés conçus pour autoriser une transaction
US10558995B2 (en) * 2011-07-29 2020-02-11 Ncr Corporation Value management system
US10032171B2 (en) 2011-08-30 2018-07-24 Simplytapp, Inc. Systems and methods for secure application-based participation in an interrogation by mobile device
US10438196B2 (en) 2011-11-21 2019-10-08 Mozido, Inc. Using a mobile wallet infrastructure to support multiple mobile wallet providers
US10395227B2 (en) 2015-01-14 2019-08-27 Tactilis Pte. Limited System and method for reconciling electronic transaction records for enhanced security
US10037528B2 (en) 2015-01-14 2018-07-31 Tactilis Sdn Bhd Biometric device utilizing finger sequence for authentication
US9607189B2 (en) 2015-01-14 2017-03-28 Tactilis Sdn Bhd Smart card system comprising a card and a carrier
CN105391541B (zh) * 2015-09-30 2019-02-19 金邦达有限公司 一种卡片个人化数据处理装置及方法
US10546444B2 (en) 2018-06-21 2020-01-28 Capital One Services, Llc Systems and methods for secure read-only authentication
US10769299B2 (en) 2018-07-12 2020-09-08 Capital One Services, Llc System and method for dynamic generation of URL by smart card
CN109359117B (zh) * 2018-08-13 2022-05-27 创新先进技术有限公司 一种卡片数据的更新方法和装置
KR20210065109A (ko) 2018-10-02 2021-06-03 캐피탈 원 서비시즈, 엘엘씨 비접촉식 카드의 암호화 인증을 위한 시스템 및 방법
US10949520B2 (en) 2018-10-02 2021-03-16 Capital One Services, Llc Systems and methods for cross coupling risk analytics and one-time-passcodes
AU2019355436A1 (en) 2018-10-02 2021-04-15 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
WO2020072583A1 (fr) 2018-10-02 2020-04-09 Capital One Services, Llc Systèmes et procédés d'établissement d'identité pour retrait de commande
US10554411B1 (en) 2018-10-02 2020-02-04 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10505738B1 (en) 2018-10-02 2019-12-10 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
JP2022508026A (ja) 2018-10-02 2022-01-19 キャピタル・ワン・サービシーズ・リミテッド・ライアビリティ・カンパニー 非接触カードの暗号化認証のためのシステムおよび方法
US10565587B1 (en) 2018-10-02 2020-02-18 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10582386B1 (en) 2018-10-02 2020-03-03 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10581611B1 (en) 2018-10-02 2020-03-03 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10511443B1 (en) 2018-10-02 2019-12-17 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
WO2020072575A1 (fr) 2018-10-02 2020-04-09 Capital One Services, Llc Systèmes et procédés d'authentification cryptographique de cartes sans contact
US10489781B1 (en) 2018-10-02 2019-11-26 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US10607214B1 (en) 2018-10-02 2020-03-31 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
WO2020072474A1 (fr) 2018-10-02 2020-04-09 Capital One Services, Llc Systèmes et procédés d'authentification cryptographique des cartes sans contact
US10592710B1 (en) 2018-10-02 2020-03-17 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
WO2020072694A1 (fr) 2018-10-02 2020-04-09 Capital One Services, Llc Systèmes et procédés d'authentification cryptographique de cartes sans contact
US10542036B1 (en) 2018-10-02 2020-01-21 Capital One Services, Llc Systems and methods for signaling an attack on contactless cards
KR20210068028A (ko) 2018-10-02 2021-06-08 캐피탈 원 서비시즈, 엘엘씨 비접촉식 카드의 암호화 인증을 위한 시스템 및 방법
US10771254B2 (en) 2018-10-02 2020-09-08 Capital One Services, Llc Systems and methods for email-based card activation
US10909527B2 (en) 2018-10-02 2021-02-02 Capital One Services, Llc Systems and methods for performing a reissue of a contactless card
US10680824B2 (en) 2018-10-02 2020-06-09 Capital One Services, Llc Systems and methods for inventory management using cryptographic authentication of contactless cards
WO2020072552A1 (fr) 2018-10-02 2020-04-09 Capital One Services, Llc Systèmes et procédés pour authentification cryptographique de cartes sans contact
US11210664B2 (en) 2018-10-02 2021-12-28 Capital One Services, Llc Systems and methods for amplifying the strength of cryptographic algorithms
KR20210066798A (ko) 2018-10-02 2021-06-07 캐피탈 원 서비시즈, 엘엘씨 비접촉식 카드의 암호화 인증을 위한 시스템 및 방법
US10579998B1 (en) 2018-10-02 2020-03-03 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
WO2020072529A1 (fr) 2018-10-02 2020-04-09 Capital One Services, Llc Systèmes et procédés d'authentification cryptographique de cartes sans contact
WO2020072670A1 (fr) 2018-10-02 2020-04-09 Capital One Services, Llc Systèmes et procédés pour l'authentification cryptographique de cartes sans contact
US10771253B2 (en) 2018-10-02 2020-09-08 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
CA3115084A1 (fr) 2018-10-02 2020-04-09 Capital One Services, Llc Systemes et procedes d'authentification cryptographique de cartes sans contact
US20200226581A1 (en) 2019-01-11 2020-07-16 Capital One Services, Llc Systems and methods for touch screen interface interaction using a card overlay
US11037136B2 (en) 2019-01-24 2021-06-15 Capital One Services, Llc Tap to autofill card data
US10510074B1 (en) 2019-02-01 2019-12-17 Capital One Services, Llc One-tap payment using a contactless card
US10467622B1 (en) 2019-02-01 2019-11-05 Capital One Services, Llc Using on-demand applications to generate virtual numbers for a contactless card to securely autofill forms
US11120453B2 (en) 2019-02-01 2021-09-14 Capital One Services, Llc Tap card to securely generate card data to copy to clipboard
US10425129B1 (en) 2019-02-27 2019-09-24 Capital One Services, Llc Techniques to reduce power consumption in near field communication systems
US10523708B1 (en) 2019-03-18 2019-12-31 Capital One Services, Llc System and method for second factor authentication of customer support calls
US10643420B1 (en) 2019-03-20 2020-05-05 Capital One Services, Llc Contextual tapping engine
US10984416B2 (en) 2019-03-20 2021-04-20 Capital One Services, Llc NFC mobile currency transfer
US10535062B1 (en) 2019-03-20 2020-01-14 Capital One Services, Llc Using a contactless card to securely share personal data stored in a blockchain
US10438437B1 (en) 2019-03-20 2019-10-08 Capital One Services, Llc Tap to copy data to clipboard via NFC
US10970712B2 (en) 2019-03-21 2021-04-06 Capital One Services, Llc Delegated administration of permissions using a contactless card
US10467445B1 (en) 2019-03-28 2019-11-05 Capital One Services, Llc Devices and methods for contactless card alignment with a foldable mobile device
US11521262B2 (en) 2019-05-28 2022-12-06 Capital One Services, Llc NFC enhanced augmented reality information overlays
US10516447B1 (en) 2019-06-17 2019-12-24 Capital One Services, Llc Dynamic power levels in NFC card communications
US11392933B2 (en) 2019-07-03 2022-07-19 Capital One Services, Llc Systems and methods for providing online and hybridcard interactions
US11694187B2 (en) 2019-07-03 2023-07-04 Capital One Services, Llc Constraining transactional capabilities for contactless cards
US10871958B1 (en) 2019-07-03 2020-12-22 Capital One Services, Llc Techniques to perform applet programming
US12086852B2 (en) 2019-07-08 2024-09-10 Capital One Services, Llc Authenticating voice transactions with payment card
US10713649B1 (en) 2019-07-09 2020-07-14 Capital One Services, Llc System and method enabling mobile near-field communication to update display on a payment card
US10885514B1 (en) 2019-07-15 2021-01-05 Capital One Services, Llc System and method for using image data to trigger contactless card transactions
US10498401B1 (en) 2019-07-15 2019-12-03 Capital One Services, Llc System and method for guiding card positioning using phone sensors
US11182771B2 (en) 2019-07-17 2021-11-23 Capital One Services, Llc System for value loading onto in-vehicle device
US10832271B1 (en) 2019-07-17 2020-11-10 Capital One Services, Llc Verified reviews using a contactless card
US10733601B1 (en) 2019-07-17 2020-08-04 Capital One Services, Llc Body area network facilitated authentication or payment authorization
US11521213B2 (en) 2019-07-18 2022-12-06 Capital One Services, Llc Continuous authentication for digital services based on contactless card positioning
US10506426B1 (en) 2019-07-19 2019-12-10 Capital One Services, Llc Techniques for call authentication
US10541995B1 (en) 2019-07-23 2020-01-21 Capital One Services, Llc First factor contactless card authentication system and method
AU2019469080A1 (en) 2019-10-02 2022-04-21 Capital One Services, Llc Client device authentication using contactless legacy magnetic stripe data
US10862540B1 (en) 2019-12-23 2020-12-08 Capital One Services, Llc Method for mapping NFC field strength and location on mobile devices
US11615395B2 (en) 2019-12-23 2023-03-28 Capital One Services, Llc Authentication for third party digital wallet provisioning
US10733283B1 (en) 2019-12-23 2020-08-04 Capital One Services, Llc Secure password generation and management using NFC and contactless smart cards
US10885410B1 (en) 2019-12-23 2021-01-05 Capital One Services, Llc Generating barcodes utilizing cryptographic techniques
US11651361B2 (en) 2019-12-23 2023-05-16 Capital One Services, Llc Secure authentication based on passport data stored in a contactless card
US10657754B1 (en) 2019-12-23 2020-05-19 Capital One Services, Llc Contactless card and personal identification system
US11113685B2 (en) 2019-12-23 2021-09-07 Capital One Services, Llc Card issuing with restricted virtual numbers
US11200563B2 (en) 2019-12-24 2021-12-14 Capital One Services, Llc Account registration using a contactless card
US10664941B1 (en) 2019-12-24 2020-05-26 Capital One Services, Llc Steganographic image encoding of biometric template information on a card
US10853795B1 (en) 2019-12-24 2020-12-01 Capital One Services, Llc Secure authentication based on identity data stored in a contactless card
US10909544B1 (en) 2019-12-26 2021-02-02 Capital One Services, Llc Accessing and utilizing multiple loyalty point accounts
US10757574B1 (en) 2019-12-26 2020-08-25 Capital One Services, Llc Multi-factor authentication providing a credential via a contactless card for secure messaging
US11038688B1 (en) 2019-12-30 2021-06-15 Capital One Services, Llc Techniques to control applets for contactless cards
US10860914B1 (en) 2019-12-31 2020-12-08 Capital One Services, Llc Contactless card and method of assembly
US11455620B2 (en) 2019-12-31 2022-09-27 Capital One Services, Llc Tapping a contactless card to a computing device to provision a virtual number
US11210656B2 (en) 2020-04-13 2021-12-28 Capital One Services, Llc Determining specific terms for contactless card activation
US11610188B2 (en) 2020-04-15 2023-03-21 Capital One Services, Llc Systems and methods for ATM integrated card fabricator
US11823175B2 (en) 2020-04-30 2023-11-21 Capital One Services, Llc Intelligent card unlock
US11030339B1 (en) 2020-04-30 2021-06-08 Capital One Services, Llc Systems and methods for data access control of personal user data using a short-range transceiver
US10861006B1 (en) 2020-04-30 2020-12-08 Capital One Services, Llc Systems and methods for data access control using a short-range transceiver
US10915888B1 (en) 2020-04-30 2021-02-09 Capital One Services, Llc Contactless card with multiple rotating security keys
US11222342B2 (en) 2020-04-30 2022-01-11 Capital One Services, Llc Accurate images in graphical user interfaces to enable data transfer
US10963865B1 (en) 2020-05-12 2021-03-30 Capital One Services, Llc Augmented reality card activation experience
US11063979B1 (en) 2020-05-18 2021-07-13 Capital One Services, Llc Enabling communications between applications in a mobile operating system
US11100511B1 (en) 2020-05-18 2021-08-24 Capital One Services, Llc Application-based point of sale system in mobile operating systems
US11216623B1 (en) 2020-08-05 2022-01-04 Capital One Services, Llc Systems and methods for controlling secured data transfer via URLs
US11062098B1 (en) 2020-08-11 2021-07-13 Capital One Services, Llc Augmented reality information display and interaction via NFC based authentication
US11683325B2 (en) 2020-08-11 2023-06-20 Capital One Services, Llc Systems and methods for verified messaging via short-range transceiver
US11165586B1 (en) 2020-10-30 2021-11-02 Capital One Services, Llc Call center web-based authentication using a contactless card
US11482312B2 (en) 2020-10-30 2022-10-25 Capital One Services, Llc Secure verification of medical status using a contactless card
US11373169B2 (en) 2020-11-03 2022-06-28 Capital One Services, Llc Web-based activation of contactless cards
US11216799B1 (en) 2021-01-04 2022-01-04 Capital One Services, Llc Secure generation of one-time passcodes using a contactless card
US11682012B2 (en) 2021-01-27 2023-06-20 Capital One Services, Llc Contactless delivery systems and methods
US11687930B2 (en) 2021-01-28 2023-06-27 Capital One Services, Llc Systems and methods for authentication of access tokens
US11792001B2 (en) 2021-01-28 2023-10-17 Capital One Services, Llc Systems and methods for secure reprovisioning
US11562358B2 (en) 2021-01-28 2023-01-24 Capital One Services, Llc Systems and methods for near field contactless card communication and cryptographic authentication
US11438329B2 (en) 2021-01-29 2022-09-06 Capital One Services, Llc Systems and methods for authenticated peer-to-peer data transfer using resource locators
US11777933B2 (en) 2021-02-03 2023-10-03 Capital One Services, Llc URL-based authentication for payment cards
US11637826B2 (en) 2021-02-24 2023-04-25 Capital One Services, Llc Establishing authentication persistence
US11245438B1 (en) 2021-03-26 2022-02-08 Capital One Services, Llc Network-enabled smart apparatus and systems and methods for activating and provisioning same
US11961089B2 (en) 2021-04-20 2024-04-16 Capital One Services, Llc On-demand applications to extend web services
US11935035B2 (en) 2021-04-20 2024-03-19 Capital One Services, Llc Techniques to utilize resource locators by a contactless card to perform a sequence of operations
US11902442B2 (en) 2021-04-22 2024-02-13 Capital One Services, Llc Secure management of accounts on display devices using a contactless card
US11354555B1 (en) 2021-05-04 2022-06-07 Capital One Services, Llc Methods, mediums, and systems for applying a display to a transaction card
US12041172B2 (en) 2021-06-25 2024-07-16 Capital One Services, Llc Cryptographic authentication to control access to storage devices
US12061682B2 (en) 2021-07-19 2024-08-13 Capital One Services, Llc System and method to perform digital authentication using multiple channels of communication
US12062258B2 (en) 2021-09-16 2024-08-13 Capital One Services, Llc Use of a payment card to unlock a lock
US12069173B2 (en) 2021-12-15 2024-08-20 Capital One Services, Llc Key recovery based on contactless card authentication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0623903A2 (fr) * 1993-05-06 1994-11-09 Pitney Bowes Inc. Système de rechargement du solde d'une carte à circuit intégré
WO1997039424A1 (fr) * 1996-04-15 1997-10-23 Ubiq Incorporated Systeme et appareil de personnalisation des cartes a puce

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS60160491A (ja) * 1984-01-31 1985-08-22 Toshiba Corp Ｉｃカードとｉｃカード発行装置
JPS63231692A (ja) * 1987-03-20 1988-09-27 Mitsubishi Electric Corp 機密コ−ド書込装置
DE3906349A1 (de) * 1989-03-01 1990-09-13 Hartmut Hennige Verfahren und vorrichtung zur vereinfachung des gebrauchs einer vielzahl von kreditkarten u. dgl.
JP2854636B2 (ja) * 1989-11-30 1999-02-03 株式会社東芝 携帯可能媒体の発行装置及び発行方法
FR2673476B1 (fr) * 1991-01-18 1996-04-12 Gemplus Card Int Procede securise de chargement de plusieurs applications dans une carte a memoire a microprocesseur.
FR2676291A1 (fr) * 1991-05-06 1992-11-13 Bull Sa Dispositif de securite pour systeme informatique et procede de reprise d'exploitation.
US5745571A (en) * 1992-03-30 1998-04-28 Telstra Corporation Limited Cryptographic communications method and system
US5530232A (en) * 1993-12-22 1996-06-25 Datamark Services, Inc. Multi-application data card
FR2737045B1 (fr) * 1995-07-21 1997-08-29 Commissariat Energie Atomique Structure photosensible durcie aux rayonnements electromagnetiques durs et son application aux cameras video
DE19536169A1 (de) * 1995-09-29 1997-04-03 Ibm Multifunktionale Chipkarte
US5991411A (en) * 1996-10-08 1999-11-23 International Business Machines Corporation Method and means for limiting adverse use of counterfeit credit cards, access badges, electronic accounts or the like

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0623903A2 (fr) * 1993-05-06 1994-11-09 Pitney Bowes Inc. Système de rechargement du solde d'une carte à circuit intégré
WO1997039424A1 (fr) * 1996-04-15 1997-10-23 Ubiq Incorporated Systeme et appareil de personnalisation des cartes a puce

Also Published As

Publication number Publication date
EP1076875A1 (fr) 2001-02-21
ATE263992T1 (de) 2004-04-15
ES2221379T3 (es) 2004-12-16
TW522350B (en) 2003-03-01
DE69916260D1 (de) 2004-05-13
CN1308750A (zh) 2001-08-15
CA2330625C (fr) 2006-04-04
DE69916260T2 (de) 2005-03-10
CA2330625A1 (fr) 1999-11-11
JP4170590B2 (ja) 2008-10-22
NZ508577A (en) 2001-11-30
JP2002513977A (ja) 2002-05-14
US6199762B1 (en) 2001-03-13
AU3784899A (en) 1999-11-23
EP1076875A4 (fr) 2003-03-12
WO1999057675A1 (fr) 1999-11-11
HK1033191A1 (en) 2001-08-17
BR9910222A (pt) 2001-01-09
AU762962B2 (en) 2003-07-10

Similar Documents

Publication Publication Date Title
EP1076875B1 (fr) Procede et appareil de personnalisation et de synchronisation dynamique de carte a puce
US7325724B2 (en) Method for registering a biometric for use with a smartcard
US7451924B2 (en) System for biometric security using a smartcard
US7506806B2 (en) Smartcard transaction method and system using fingerprint recognition
US7314165B2 (en) Method and system for smellprint recognition biometrics on a smartcard
US7793845B2 (en) Smartcard transaction system and method
US7445149B2 (en) System for biometric security using a smartcard
CA2570739C (fr) Systeme de securite biometrique au moyen d'une carte a puce
US20060000899A1 (en) Method and system for dna recognition biometrics on a smartcard
US20060000897A1 (en) Method and system for signature recognition biometrics on a smartcard
US20060016868A1 (en) Method and system for hand geometry recognition biometrics on a smartcard
AU2336299A (en) Methods and apparatus for a travel-related multi-function smartcard
US20060016869A1 (en) Method and system for auditory emissions recognition biometrics on a smartcard
US20060020558A1 (en) Method and system for proffering multiple biometrics for use with a smartcard
US20060016874A1 (en) System for registering a biometric for use with a smartcard
MXPA00010766A (es) Metodos y aparatos para sincronizacion y personalizacion dinamicas de tarjeta inteligente

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20001124

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

A4 Supplementary search report drawn up and despatched

Effective date: 20030124

RIC1 Information provided on ipc code assigned before grant

Ipc: 7G 06K 7/00 B

Ipc: 7G 07F 7/10 A

17Q First examination report despatched

Effective date: 20030312

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20040407

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20040407

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20040407

Ref country code: CH

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20040407

Ref country code: BE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20040407

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20040504

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20040504

REF Corresponds to:

Ref document number: 69916260

Country of ref document: DE

Date of ref document: 20040513

Kind code of ref document: P

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20040531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20040707

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20040707

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1033191

Country of ref document: HK

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2221379

Country of ref document: ES

Kind code of ref document: T3

ET Fr: translation filed
REG Reference to a national code

Ref country code: IE

Ref legal event code: MM4A

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20050110

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20040907

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: NL

Payment date: 20120515

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: SE

Payment date: 20120511

Year of fee payment: 14

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 69916260

Country of ref document: DE

Representative=s name: MUELLER-BORE & PARTNER PATENTANWAELTE, EUROPEA, DE

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20130124 AND 20130130

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 69916260

Country of ref document: DE

Representative=s name: MUELLER-BORE & PARTNER PATENTANWAELTE PARTG MB, DE

Effective date: 20130114

Ref country code: DE

Ref legal event code: R082

Ref document number: 69916260

Country of ref document: DE

Representative=s name: MUELLER-BORE & PARTNER PATENTANWAELTE, EUROPEA, DE

Effective date: 20130114

Ref country code: DE

Ref legal event code: R081

Ref document number: 69916260

Country of ref document: DE

Owner name: SORA APPLICATIONS LLC, DOVER, US

Free format text: FORMER OWNER: AMERICAN EXPRESS TRAVEL RELATED SERVICES COMPANY, INC., NEW YORK, N.Y., US

Effective date: 20130114

Ref country code: DE

Ref legal event code: R081

Ref document number: 69916260

Country of ref document: DE

Owner name: SORA APPLICATIONS LLC, US

Free format text: FORMER OWNER: AMERICAN EXPRESS TRAVEL RELATED SERVICES COMPANY, INC., NEW YORK, US

Effective date: 20130114

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: SORA APPLICATIONS LLC, US

Effective date: 20130214

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: AT

Payment date: 20120426

Year of fee payment: 14

REG Reference to a national code

Ref country code: ES

Ref legal event code: PC2A

Owner name: SORA APPLICATIONS LLC

Effective date: 20130415

REG Reference to a national code

Ref country code: NL

Ref legal event code: V1

Effective date: 20131201

REG Reference to a national code

Ref country code: SE

Ref legal event code: EUG

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 263992

Country of ref document: AT

Kind code of ref document: T

Effective date: 20130531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130505

Ref country code: AT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20130531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20131201

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20150514

Year of fee payment: 17

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20150513

Year of fee payment: 17

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 18

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160504

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 19

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20170531

Year of fee payment: 19

Ref country code: GB

Payment date: 20170426

Year of fee payment: 19

Ref country code: FR

Payment date: 20170418

Year of fee payment: 19

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20160505

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20181128

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 69916260

Country of ref document: DE

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20180504

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180504

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20180531

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20181201