PCI Watch

Tracking changes across the Payment Card Industry

SB n° 229: EMV® QR Code Merchant-Presented Mode RFU Processing and New Data Objects

v1.0 Specification Bulletins
QR Code

EMV<sup>®</sup> Specification Bulletin No. 229 First Edition July 2019 EMV QR Code Merchant-Presented Mode RFU Processing and New Data Objects This Specification Bulletin:

  • Clarifies the expected mobile application behaviour when encountering data objects and data values that are Reserved for Future Use (RFU).
  • Adds the optional data object Merchant Tax ID.
  • Adds the optional data object Merchant Channel. This Specification Bulletin describes proposed changes to EMV QR Code Specification for Payment Systems, Merchant-Presented Mode, version 1.0 [MPM].

Applicability

This Specification Bulletin applies to:

  • EMV QR Code Specification for Payment Systems, Merchant-Presented Mode, version 1.0 [MPM]

Related Documents

  • None

Effective Date

  • Immediately

Description

This bulletin:

  • Clarifies that mobile applications must ignore the presence of a data object or data value that is Reserved for Future Use (RFU) by EMVCo. It has been noted that some mobile applications terminate the transaction on reading data objects or data values that are defined as RFU in the specification. However, to allow for migration and support of new functionality, the mobile application must not verify the data or data value indicated as RFU.
  • Adds the optional data object Merchant Tax ID to the merchant presented QR Code. The Merchant Tax ID contains the tax identification number of the merchant.
  • Adds the optional data object Merchant Channel. The Merchant Channel indicates the environment a QR Code is presented to the consumer. Specification Changes countries. In Section 1.4 Data Objects, add the following new sub-section:

1.4.4 Reserved for Future Use (RFU) While the QR Code is required to not contain data objects that are RFU, the mobile application must ignore RFU data object IDs and data object values if present in the QR Code. In Section 3.1 QR Code Payload, Table 3.5: Additional Data Objects, add the following entries to the end of the table: Merchant Tax ID The tax identification number of the merchant, assigned by the governmental body of the country in which the EMV merchantpresented QR code is being used/displayed. For example, the Merchant Tax ID may be used by the consumer mobile application for receipt display. Merchant Channel A merchant channel establishes the environment a QR Code is presented to the consumer. Covering use cases such as retail outlet, Ecommerce, bill payment with the purpose of improving transaction reporting. In Section 3.2 Data Organization, Table 3.7: Data Objects for Additional Data Field Template (ID "62"):

  • Add the following entries after the entry for "Additional Consumer Data Request": Merchant Tax ID "10" ans var. up to "20" O Merchant Channel "11" ans "03" O
  • In the entry for "RFU for EMVCo", change the ID from "'10' – '49'" to "'12' – '49'". In Section 4.5 Data Object Values, add the following new sub-section:

4.5.4 Reserved for Future Use (RFU) 4.5.4.1 Data object IDs and data object values that are defined as RFU shall not be included in the QR Code. In Section 4.8 Data Objects – Additional Data Field Template (ID "62"), add the following new subsection:

4.8.1.6 If present, each of the three positions in the Merchant Channel (ID "11") identifies a characteristic of the channel used for a particular transaction. The values defined and meaning of the values are listed below. All other values not explicitly listed in the tables shall be RFU. First Character – Media

countries.

Value "0" "1" "2" "3" "4" "5" "6" "7" Meaning Print

  • Merchant sticker Print
  • Bill/Invoice Print
  • Magazine/Poster Print
  • Other Screen/Electronic
  • Merchant Screen/Electronic
  • Website Screen/Electronic
  • App Screen/Electronic
  • Other POS/POI Value "0" "1" "2" "3" Second Character – Transaction Location Meaning At Merchant premises/registered address Not at Merchant premises/registered address Remote Commerce Other Value "0" "1" "2" "3" Third Character – Merchant Presence Meaning Attended POI Unattended Semi-attended (self-checkout) Other In Section 4.8 Data Objects – Additional Data Field Template (ID "62"), Table 4.3: Data Object ID Allocation in Additional Data Field Template with ID "62": change the ID ""10"-"49"" to ""12"-49"". Annex A – Data Objects Dictionary countries. Table A.1: QR Code Data Objects Dictionary Merchant Tax ID F: ans ID: "10" L: var. up to "20" Merchant Channel F: ans ID: "11" L: "03" "62" The tax identification number of the Please refer to merchant. 4.8. "62" A three character value that Please refer to corresponds to the method used to 4.8. present the QR code by the merchant including: display method, transaction location and merchant presence. Annex B – Merchant Channel Use Cases Table B.8: Examples of Merchant Channel Use Cases Use Cases Media Transaction Location Retail outlet Retail outlet selfcheckout Vending machine, petrol station Street vendors, Markets Ecommerce / Website Bill payment Magazine / Poster Screen (Merchant POS) Print (Merchant sticker) Screen (Merchant POS) Print (Merchant sticker) Screen (Merchant POS) Print (Merchant sticker) Screen (App) Print (Merchant sticker) Screen (Website) Print (Bill/Invoice) Print (Magazine/Poster) At Merchant At Merchant At Merchant Not at Merchant Remote Not at Merchant Not at Merchant Merchant Presence Attended Semi-attended Unattended Attended Unattended Unattended Unattended Value "400" "000" "402" "002" "401" "001" "610" "010" "521" "111" "211" countries.

Legal Notice

The EMV<sup>®</sup> Specifications are provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in these Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AS TO THESE SPECIFICATIONS. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to determine whether any implementation of the EMV<sup>®</sup> Specifications may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of the EMV<sup>®</sup> Specifications should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, the Specifications may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement these Specifications is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party’s infringement of any intellectual property rights in connection with the EMV<sup>®</sup> Specifications

countries.