WO2012096979A1 - Procédé et système utilisant un bitmap pour passer des variables de transactions par carte de paiement sans contact dans des formats de données normalisés - Google Patents

Procédé et système utilisant un bitmap pour passer des variables de transactions par carte de paiement sans contact dans des formats de données normalisés Download PDF

Info

Publication number
WO2012096979A1
WO2012096979A1 PCT/US2012/020807 US2012020807W WO2012096979A1 WO 2012096979 A1 WO2012096979 A1 WO 2012096979A1 US 2012020807 W US2012020807 W US 2012020807W WO 2012096979 A1 WO2012096979 A1 WO 2012096979A1
Authority
WO
WIPO (PCT)
Prior art keywords
card
bitmap
payment
mobile device
proximity
Prior art date
Application number
PCT/US2012/020807
Other languages
English (en)
Inventor
Patrik Smets
Eddy Lodewijk Hortensia Van De Velde
Original Assignee
Mastercard International Incorporated
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
Priority claimed from US12/987,616 external-priority patent/US8439271B2/en
Application filed by Mastercard International Incorporated filed Critical Mastercard International Incorporated
Publication of WO2012096979A1 publication Critical patent/WO2012096979A1/fr

Links

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • 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
    • 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/08—Payment architectures
    • G06Q20/20—Point-of-sale [POS] network systems
    • 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/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/327—Short range or proximity payments by means of M-devices
    • 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/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

  • plastic cards for payment transactions is ubiquitous modern economy. All involved parties e.g., the payment card industry, consumers, banks and merchants have an interest in making these card-based payment transactions secure and fraud-proof.
  • plastic cards have a magnetic stripe added to the back of the cards in which card holder information and other security and encryption codes are stored in machine-readable form.
  • the machine-readable nature of the data makes it more resistant to tampering or forgery.
  • the physical structure and data content of the magnetic stripes are standardized to achieve desirable interoperability (e.g., most ATM cards work at every money machine in the world).
  • industry standards organizations and groups e.g., International Organization for Standards (ISO) and International Electro Technical Committee (IEC)
  • ISO/IEC 7811 ISO/IEC 7811
  • ISO 7811 ISO/IEC 7811
  • Track 1 which was developed by the International Air Transportation Association (IATA), is 210 bpi with room for 79 7-bit characters. Track 1 is encoded with a 7-bit scheme (6 data bits plus one parity bit) based on ASCII. The seventh bit is an odd parity bit at the end of each byte.
  • Track 2 which was developed by the American Bankers Association (ABA) for online financial transactions, is 75 bpi with room for 40 5-bit numeric characters.
  • Track 3 which is also used for financial transactions, is 210 bpi with room for 107 numeric digits.
  • Track 1 further delimits data fields in the Tracks and reserves them for specific information.
  • Track 1 for example, includes designated data fields for specific information such as Primary Account Number, Country Code, Surname, First Name or Initial, Middle Name or Initial, Title, and Expiration Date, etc.
  • the data is encoded in ASCII.
  • Table 2 shows the standardized data field format recommended for Track 2.
  • Each of the three Tracks includes a data field, which is reserved for individual use by the card issuer or vendor. Card issuers or vendors often utilize the reserved data field, which is labeled "discretionary data", to store a static
  • CVC1 numeric card validation code value
  • MasterCard assignee MasterCard International Incorporated (“MasterCard”) prefers to store a numeric card validation code value (CVC1) in the Track 2 discretionary data field.
  • CVC1 value which is a three digit encrypted number, can be checked to ensure that the magnetic stripe information has not been altered in any way.
  • Other card vendors or issuers may store other codes or values in the discretionary data field, or none at all.
  • the card reader/terminal For processing a transaction, the card reader/terminal reads the formatted data, which is recorded in the card's magnetic stripe Tracks.
  • the formatted data may be transmitted to an issuer or bank for validation or approval of the transaction.
  • the payment card industry is now exploiting developments in semiconductor device technologies to build in more functionality and features in the plastic payment cards.
  • smart cards that contain an actual integrated circuit chip, and contactless cards that use a magnetic field or radio frequency identification (RFID) tags for close-proximity reading are now available.
  • RFID radio frequency identification
  • the built-in electronic processing features of the smart cards and/or proximity cards make it possible deploy more rigorous solutions for securing card use and preventing fraud.
  • some available smart cards are configured to perform "on card" cryptographic functions for security solutions based on digital signatures.
  • PayPass PayPass Specification
  • a security solution which may be utilized in PayPass, is based on generation of a dynamic authentication value or number (CVC3).
  • CVC3 dynamic authentication value
  • the dynamic authentication value changes with each transaction.
  • an unauthorized person obtains the CVC3 number for a particular transaction, the unauthorized person cannot use that CVC3 number as the authentication value for the next or any other transactions.
  • Any electronic payment system based on the new card technologies is likely to gain acceptance by users only if the new system is backwards compatible with legacy infrastructure (e.g., terminals, card readers, and back office operations), which was designed for processing magnetic stripe cards.
  • legacy infrastructure e.g., terminals, card readers, and back office operations
  • CVC3 dynamic authentication value
  • other proximity card function specific data to the issuer or other validating party in a format which does not disturb the data fields or information required by ISO 7811 for magnetic stripe card transactions.
  • the CVC3 number and other proximity card function specific data should be placed in a discretionary data field of a magnetic stripe Track data fomiat in the expectation that the standardized data fields required for magnetic stripe card operation will not be disturbed.
  • usage of the discretionary data fields by vendors and issuers is not consistent.
  • the static authentication values e.g., CVC2
  • the space available in the discretionary data fields for placing the CVC3 number may vary from card to card according to vendor encoding of the discretionary data fields. This varying availability of discretionary data space makes it difficult to standardize use of the space for storing proximity card function related data (e.g., CVC3).
  • proximity payment card implementations compatible with existing standardized magnetic stripe payment card transaction processes. Attention is being directed to the development of proximity payment cards that can be used with existing magnetic stripe card infrastructure and processes. In particular, attention is being directed to the formatting of proximity function related data in a manner that does not disturb existing standardized data structures or information used in the magnetic stripe card transactions.
  • the present invention provides a standardization method and a system for communicating proximity card transaction data in a form which is compatible with installed electronic payment systems or infrastructure for processing magnetic stripe card transactions.
  • the standardization method and system place or integrate the proximity payment card transaction data (e.g., dynamic authentication codes) in ISO 7811 byte-level formatted data structures that are commonly used in processing magnetic stripe card transactions.
  • the proximity payment card transaction data is placed in unused portions of discretionary data fields (e.g., Track 2 discretionary data field).
  • the availability of unused space in a card's discretionary data fields can vary by card issuer or vendor.
  • An issuer or vendor-specific bitmap identifies available unused space in the discretionary data fields in the cards.
  • Dynamic authentication codes, unidentified numbers, automatic transaction counter and/or other proximity card transaction parameters are placed in the discretionary data fields in available free space, which is identified by the bitmap.
  • FIG. 1 is a diagram illustrating a numbering or indexing scheme for different digit positions in a discretionary data field.
  • FIG. 2 is a diagram illustrating the relationship between a bit map and discretionary data field digit positions.
  • FIG. 4 is a diagram illustrating an exemplary PCVC bit map OxOOEO), which identifies three useable digit positions p8, p7 and p5 in Track 2 discretionary data field (13 digits) where CVC3 digits can be placed in accordance with the principles of the present invention.
  • FIG. 5 is a schematic illustration of an electronic payment system capable of processing both proximity payment card transactions and magnetic stripe card transactions in accordance with the principles of the present invention.
  • FIG. 6 is a diagram illustrating the interactions and communications between a proximity payment card and a terminal during the conduct of an electronic transaction in accordance with the principles of the present invention.
  • FIG. 7 is a schematic illustration of an electronic payment system capable of processing both mobile device transactions and magnetic stripe card transactions in accordance with the principles of the present invention.
  • the invention provides a standardization method and system for placing proximity card function data or digits in discretionary data fields used for magnetic stripe cards.
  • the digits are stored in available space in the discretionary data fields, which has not been used by card issuers or vendors.
  • the number of such digits and their precise locations within a discretionary data field are flexibly assigned using a bitmap.
  • the bitmap is stored in the card's discretionary data field.
  • the flexible manner of placing proximity card function data or digits in the card's discretionary data fields does not have any adverse effect on card functions. Card behavior is independent of vendor usage of the discretionary data fields.
  • inventive data placement method is described herein with reference to the discretionary data field defined in Track 2.
  • inventive data placement method is readily extended to additional or alternate discretionary data fields (e.g., Track 1 discretionary data field).
  • inventive storage method is described herein using as an example the placement of a card validation code (CVC3) number, which is generated as a security measure during transaction processing.
  • CVC3 card validation code
  • the standardization method and format may be incorporated in suitable electronic payment system applications so that the system can process both proximity payment card transactions and magnetic stripe card transactions.
  • MasterCard assignee MasterCard International Incorporated
  • PaymentPass MasterCard PayPassTM ISO/IEC 14443 Implementation Specification
  • the PayPass implementation is consistent with the ISO 14443 Standard and the ISO 7811 Standard and provides a convenient example illustrating the principles of the present invention.
  • the PayPass implementation provides a "PayPass — Mag Stripe" application, which can process transactions based on proximity cards and magnetic stripe cards. (See FIG. 5).
  • the PayPass— Mag Stripe application is an extension of the currently available magnetic-stripe applications for debit and credit payments.
  • PayPass— Mag Stripe uses the same processing infrastructure as that is now used for magnetic stripe card transactions. It will be understood that the selection of the PayPass implementation for purposes of illustration is only exemplary, and that the principles of the present invention can be more generally applied to electronic payment devices and systems that operate under other common industry or proprietary standards.
  • other specifications that can be used in connection with various embodiments of the disclosed subject matter include ISO/IEC 18092 (e.g., for use with mobile devices) and ISO/IEC 7816 (e.g., for use with contact cards).
  • terminal 2 in a proximity payment card transaction between an interacting payment card (e.g., PayPass card 1) and a reader terminal 2, as part of the security procedure, terminal 2 generates and transmits to the payment card an unpredictable number (UN).
  • payment card 1 computes a CVC3 number based on a portion of the UN and transmits the computed CVC3 number to terminal.
  • Payment card 1 may use a secret encryption key stored on the card for computing the CVC3 number.
  • payment card 1 may be personalized at the card issuer option to compute the CVC3 number based on a portion of the UN and on the card's application transaction counter (ATC). In such cases, payment card 1 transmits both the computed CVC3 number and the ATC to the terminal 2.
  • ATC application transaction counter
  • a bitmap (BM) and a Position CVC3 data element (PCVC) stored on the card provide terminal 2 with rules for placing proximity payment card transaction data in discretionary data space.
  • terminal 2 packages or formats the ATC, UN, and the CVC3 number in a discretionary data field according to these rules.
  • Terminal may then communicate the discretionary data field under magnetic stripe card conventions to an acquirer host 4 and/or issuer host 5 for authorization of the transaction.
  • Terminal 2 may, for example, send the discretionary data field as part of Track 2 in Data Element 35 (DE35) of a standardized message 100 to the issuer for authorization or approval (8, 110).
  • DE35 Data Element 35
  • FIG. 1 shows a numbering or indexing of different positions in a discretionary data field (e.g. Track 2 discretionary data field).
  • the number of digits present in discretionary data is indicated by the index m.
  • Card vendors and issuers use part of discretionary data field for legacy payment systems. As a result, only a small part of discretionary data field is available as vehicle for transporting PayPass data. Therefore, flexibility in using different combinations of UN and ATC as well as positioning these data elements in the discretionary data field is required.
  • the CVC3 number is generated by the PayPass card by employing a diversified secret key and the following input data: the static part of the Track data; the ATC of the card, and the UN provided by the terminal. Not all of the input data types are or need to be used in every instance.
  • different combinations of input data may be used to generate the CVC3 number.
  • FIG. 2 shows the relationship between a bitmap and the discretionary data field's digit positions.
  • Each bit in the bitmap refers to a position in the discretionary data field.
  • the least significant bit of the bitmap i.e., the rightmost bit bi
  • the number of bits q in the bitmap is always a multiple of 8.
  • the number q is related to the number of discretionary data field digits m by the equation:
  • Track 2 Data For Track 2 discretionary data field (“Track 2 Data”), m is a maximum of 13 digits, resulting in a bitmap of 16 bits or 2 bytes.
  • Track 1 Data For Track 1 discretionary data Field (“Track 1 Data”), the maximum value of m is 48, resulting in a bitmap of length 6 bytes or 48 bits.
  • Specific bitmaps used in PayPass applications may indicate specific positions in Track 2 Data for placing UN and ATC.
  • Another bitmap, Position CVC3 (PCVC) may be used to indicate specific positions in Track 2 Data for placing the CVC3 number.
  • the bitmaps are card parameters that can be personalized as desired by the card issuers or vendors.
  • a card issuer retains full flexibility on the number, position and usage of PayPass data (digits).
  • the terminal places UN and ATC digits at locations in discretionary data, which are specified by the issuer at the card personalization stage. Further, the terminal also places the CVC3 digits according to the vendor-specified bitmap.
  • the terminal is assigned the chore of conversion from binary to BCD. This assignment reduces card complexity and improves transaction performance. As the terminal processes or applications do the entire filling or placing of the discretionary data fields, on-card processes do not have to be concerned with or aware of the bitmaps.
  • on-card processes are always the same, independent of the values of the bitmaps.
  • the on-card computation always uses the full ATC (i.e., the full two bytes).
  • the terminal converts the ATC from binary coding to BCD coding and populates the discretionary data with the least significant part of the ATC digits as indicated by the bitmap.
  • Card behavior is independent of the number of ATC digits placed and the locations of such digits in the discretionary data fields.
  • the card includes the full UN as received from the terminal in the CVC3 computation.
  • the terminal processes provide a UN with leading zeroes as indicated by the bitmaps, so that only the relevant parts of UN are placed in the discretionary data field. For example, if a particular card issuer specified bitmap indicates that only three (3) UN digits are to be placed in the discretionary data field, then the terminal must send a UN with five (5) leading zeroes as the UN length is always eight (8) digits (e.g., if the value of the UN is 123, then the terminal will send 00000123 to the card).
  • the card will include the full eight-digit UN 00000123 in the computation of the CVC3, while the terminal will place only the three digits 123 in the discretionary data field. If for another card, the issuer-specified bitmap indicates that six (6) UN digits are to be included in the discretionary data field, then the terminal must send a UN with two (2) leading zeroes (e.g., if the value of the UN is 456789, then the terminal will send 00456789 to the card). The card will include the full eight-digit 00456789 in the calculation of the CVC3, while the terminal will place only the six digits 456789 in the discretionary data field. These examples show that the card behavior is independent of the number of UN digits included in the discretionary data field, as well as of their position in the discretionary data field.
  • a CVC3 number returned by a card is always two (2) bytes long and in binary format.
  • the terminal converts the CVC3 to BCD value and decides on the number of CVC3 digits to place in the discretionary data field, based on a PCVC bitmap.
  • FIG. 4 shows an exemplary PCVC bitmap 0xOOEO, which like the bitmaps for UN or ATC placement, ensures that on-card processes and transaction functions are independent of the number and location of CVC3 digits placed in the discretionary data field.
  • FIG. 6 shows the interactions and communications that may occur between a PayPass card and a terminal during the conduct of transaction 100 (FIG. 5) using the exemplary PayPass— Mag Stripe application.
  • the terminal selects the PayPass — Mag Stripe application.
  • the card responds with a file control information request.
  • the requested information may include a list of tags and lengths of terminal-resident data elements (PDOL) needed by the card for further transaction processing.
  • the terminal issues a command (GET PROCESSING OPTIONS), which may mclude the requested PDOL information.
  • the card returns indicators ( ⁇ and AFL) which indicate that all data to be read by the terminal are included in record 1 of the file with SF1 1.
  • the terminal issues a command (READ RECORD) to retrieve the static data from the card, and the card returns the appropriate Track 1 and Track 2 data and bitmaps.
  • the terminal issues a command (COMPUTE CRYPTOGRAPHIC
  • CHECKSUM using a data field which is the concatenated list of data elements resulting from processing an unpredictable number data object list (UDOL) returned by the card at step 106.
  • This command initiates the computation of a dynamic CVC3 Track 2 number in the PayPass card. Additionally or alternatively, a dynamic CVC3 Track 1 number may be computed. The computation uses a secret key stored in the card and is based on the UN sent by the terminal and/or the ATC of the card. At step 109, the card sends the ATC and the computed CVC3 Track 2 and/or Track 1 numbers to the terminal.
  • the terminal uses the inventive bitmap guided procedure using bitmaps provided by the card. (See FIGS. 2-4).
  • the terminal converts the binary CVC3 Track 2 number into BCD encoded digits and copies the relevant digits in the discretionary data field of the Track 2 Data at the places indicated by a bitmap ("Track 2 BitMap for CVC3 (PCVC3 Track2 )") provided by the card.
  • the terminal also copies the relevant digits of UN into the discretionary data field of the Track 2 Data.
  • the number of UN digits (n UN ) is copied in the least significant digit of the discretionary data field.
  • a bitmap (“Track 2 BitMap for UN”) indicates where the terminal must copy the UN digits in the discretionary data field of the Track 2 Data.
  • the terminal converts the ATC into BCD encoded digits and copies relevant ATC digits into the discretionary data field of the Track 2 Data at the places indicated by a bitmap ("Track 2 Bitmap for ATC (PUNATC Track
  • the terminal may use a similar bitmap guided procedure to place data in Track 1 discretionary data fields, in cases where the card returns Track 1 data (step 106) in response to the READ RECORD command (step 105).
  • the terminal For the Track 1 Data, the terminal first converts the data returned by the card into ASCII encoded characters before copying them into the discretionary data.
  • a cellular telephone may be used for payment, as shown in FIG. 7.
  • the cellular phone has an antenna which may be used for communicating with other mobile devices and with a transaction terminal.
  • the cellular phone also includes a memory device for storing a bitmap as described above.
  • the cellular phone further includes a processing unit such as a Secure Element such as a SIM card having a secure memory or a phone processor which can perform the functions performed by a integrated circuit chip for a payment card.
  • the PayPass implementation can be used to process transactions based on mobile devices such as cellular phones, Alternatively, any other suitable implementation specification may be used, including ISO/IEC 18092.
  • a reader terminal can generate an unpredictable number (UN) and transmit the UN to the mobile phone.
  • the mobile device computes a CVC3 number based on the UN and transmits the computed CVC3 number to the terminal.
  • the transaction is then processed as previously described.
  • the disclosed subject matter can be used in conjunction with a contact card.
  • contact card refers to a payment token which must come into contact with the payment terminal, but does not require that the magstripe be swiped as in conventional systems.
  • the ISO/IEC 7816 implementation specification, or any other suitable implementation specification, can be used.
  • the contact card includes a contact plate.
  • the contact card can he a 7816 contact plate.
  • the contact card can receive an unpredictable number, generate a CVC3 number based on the unpredictable number, and transmit the CVC3 number to the terminal.
  • An integrated circuit chip in the contact card can use a bitmap stored in a memory device to generate the CVC3 number. The transaction is then processed as previously described.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Microelectronics & Electronic Packaging (AREA)
  • Credit Cards Or The Like (AREA)

Abstract

Un système de paiement électronique est configuré pour traiter à la fois des transactions par carte de paiement de proximité et par carte à bande magnétique. Les données des transactions par carte à bande magnétique sont communiquées entre des cartes, des lecteurs et des parties autorisant ou approuvant les transactions dans des structures ou des pistes de données de la norme industrielle commune ISO 7811. Les données des transactions par carte de paiement de proximité, telles que des codes d'authentification dynamiques, sont placées dans un espace inutilisé dans les mêmes structures de données formatées standard. La disponibilité de l'espace inutilisé varie avec l'émetteur de carte ou le fournisseur. Un bitmap spécifique à l'émetteur fournit un index à l'espace disponible dans des champs de données discrétionnaires dans des pistes de bandes magnétiques. Le bitmap est également enregistré dans le champ de données discrétionnaires de la carte.
PCT/US2012/020807 2011-01-10 2012-01-10 Procédé et système utilisant un bitmap pour passer des variables de transactions par carte de paiement sans contact dans des formats de données normalisés WO2012096979A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12/987,616 US8439271B2 (en) 2004-07-15 2011-01-10 Method and system using a bitmap for passing contactless payment card transaction variables in standardized data formats
US12/987,616 2011-01-10

Publications (1)

Publication Number Publication Date
WO2012096979A1 true WO2012096979A1 (fr) 2012-07-19

Family

ID=46507407

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2012/020807 WO2012096979A1 (fr) 2011-01-10 2012-01-10 Procédé et système utilisant un bitmap pour passer des variables de transactions par carte de paiement sans contact dans des formats de données normalisés

Country Status (1)

Country Link
WO (1) WO2012096979A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210345639A1 (en) * 2020-05-08 2021-11-11 Pharmavite Llc Gelatin and pectin gummy composition for starchless production

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020035548A1 (en) * 2000-04-11 2002-03-21 Hogan Edward J. Method and system for conducting secure payments over a computer network
US20050127164A1 (en) * 2002-03-19 2005-06-16 John Wankmueller Method and system for conducting a transaction using a proximity device and an identifier
US20060022033A1 (en) * 2004-07-15 2006-02-02 Patrick Smets Method and system using a bitmap for passing contactless payment card transaction variables in standardized data formats
US20090303250A1 (en) * 2008-06-04 2009-12-10 Simon Phillips Card image description format to economize on data storage

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020035548A1 (en) * 2000-04-11 2002-03-21 Hogan Edward J. Method and system for conducting secure payments over a computer network
US20050127164A1 (en) * 2002-03-19 2005-06-16 John Wankmueller Method and system for conducting a transaction using a proximity device and an identifier
US20060022033A1 (en) * 2004-07-15 2006-02-02 Patrick Smets Method and system using a bitmap for passing contactless payment card transaction variables in standardized data formats
US20090303250A1 (en) * 2008-06-04 2009-12-10 Simon Phillips Card image description format to economize on data storage

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210345639A1 (en) * 2020-05-08 2021-11-11 Pharmavite Llc Gelatin and pectin gummy composition for starchless production

Similar Documents

Publication Publication Date Title
US8439271B2 (en) Method and system using a bitmap for passing contactless payment card transaction variables in standardized data formats
US7866552B2 (en) Method and system using a bitmap for passing contactless payment card transaction variables in standardized data formats
US8469277B2 (en) Methods, systems and computer program products for wireless payment transactions
EP2430601B1 (fr) Appareil, procédé et produit programme d'ordinateur pour fournir un mécanisme de contrôle de qualité pour l'interface sans contact d'une carte à double interface
US10217109B2 (en) Apparatus and method for combining cryptograms for card payments
US8712892B2 (en) Verification of a portable consumer device in an offline environment
US8010428B2 (en) Form factor identification
US20150066758A1 (en) Payment card systems and methods
US20050127164A1 (en) Method and system for conducting a transaction using a proximity device and an identifier
EP3268913A1 (fr) Carte de paiement stockant des informations segmentées en unités
WO2010126994A1 (fr) Appareil, procédé, et produit-programme d'ordinateur pour récupérer des transactions de dispositif de paiement intelligent déchirées
CN101996442A (zh) 电子钱包充值方法及其装置和系统
WO2012096979A1 (fr) Procédé et système utilisant un bitmap pour passer des variables de transactions par carte de paiement sans contact dans des formats de données normalisés

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12733888

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12733888

Country of ref document: EP

Kind code of ref document: A1