EMVCo Consumer Presented QR Specification v1 1
EMVCo Consumer Presented QR Specification v1 1
Consumer-Presented Mode
Version 1.0
July 2017
Legal Notice
The EMV® 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.
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®
Specifications.
QR Code is a registered trademark of DENSO WAVE.
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Contents Page iii of vi
Contents
1 Introduction.......................................................................................................... 7
1.1 Scope ......................................................................................................... 7
1.2 Normative References ................................................................................ 7
1.3 Notational Conventions ............................................................................... 8
1.3.1 Abbreviations .................................................................................. 8
1.3.2 Notations ......................................................................................... 9
1.3.3 Requirement Terminology and Conventions .................................... 9
1.3.4 Requirement Numbering ................................................................. 9
1.4 Data Objects ............................................................................................... 9
1.4.1 Data Object Presence ..................................................................... 9
1.4.2 Data Object Length ....................................................................... 10
1.4.3 Data Object Format Conventions .................................................. 10
2 Overview to EMV® QR Code Payment............................................................... 11
2.1 QR Code Payments .................................................................................. 11
3 EMV QR Code Payload Data Objects ................................................................ 14
3.1 QR Code Payload and Formatting ............................................................ 14
3.1.1 QR Code Payload ......................................................................... 14
3.2 QR Code Encoding ................................................................................... 16
4 QR Code Reader Requirements ........................................................................ 17
4.1 QR Code Reader ...................................................................................... 17
5 POI App Requirements ...................................................................................... 18
5.1 EMV QR Code Processing Requirements ................................................. 18
5.1.1 Decode the QR Code Data............................................................ 18
5.1.2 Verify EMV QR Code .................................................................... 18
5.1.3 Parsing and Format Validation ...................................................... 18
5.1.4 Application Template(s) ................................................................. 19
5.1.5 No Eligible Application Template ................................................... 19
5.1.6 Multiple Eligible Application Templates.......................................... 19
5.1.7 Chosen Application Template ........................................................ 20
5.1.8 Common Data Template ............................................................... 20
5.1.9 Combining Templates ................................................................... 20
5.1.10 Duplicate POI Data........................................................................ 20
5.1.11 Unrecognised Data Objects ........................................................... 20
5.1.12 Data Processing ............................................................................ 21
6 Transaction Processing ..................................................................................... 22
6.1 Check Whether Payment Product is Supported ........................................ 23
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Contents Page iv of vi
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Figures Page v of vi
Figures
Figure 2.1 QR Code Payment Architecture....................................................... 11
Figure 2.2 Consumer Device Functional View .................................................. 12
Figure 2.3 Merchant Device Functional View.................................................... 13
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Tables Page vi of vi
Tables
Table 1.1: References Materials ........................................................................ 7
Table 1.2: Abbreviations .................................................................................... 8
Table 1.3: Value Representation and Notation .................................................. 9
Table 1.4: Data Object Format Conventions .................................................... 10
Table 3.1: QR Code Payload Data .................................................................. 15
Table 6.1: List of POI Data ............................................................................... 22
Table 6.2: Track 2 Equivalent Data (Tag '57') ................................................... 23
Table 6.3: Issuer URL (Tag '5F50') ................................................................... 24
Table A.1: Data Objects .................................................................................. 26
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 7 / 32
1 Introduction
The EMV® QR Code Payment Specification (EMV QRCPS) Consumer-Presented Mode (this
specification) defines the format, encoding, and decoding of the data "payload" of the
consumer presented QR Code used to perform EMV based QR Code transactions.
1.1 Scope
The following are explicitly defined as in scope for this specification:
• The format of data encoded into the QR Code
• The QR Code Reader requirements to read and decode the data from the QR Code
• POI transaction processing on the data from the QR Code
The following are explicitly defined as outside the scope of this specification:
• Data sources used to populate the data in the QR Code
• Optical reader/scanner hardware requirements
• The mapping of data objects recovered from the QR Code into the online
authorisation request message
• Payment systems rules for QR Code transactions
• Host processing of QR Code transactions
• Use of QR Code data for non-financial transactions
[EMV] EMV ICC Specifications for Payment Systems, Version 4.3, November 2011, and
all published bulletins. Integrated Circuit Card Specifications for Payment Systems.
[EMV Bulletin EMV Specification Bulletin No. 167—Payment Account Reference (PAR)
No. 167]
[ISO 639-1] Codes for the representation of names of languages—Part 1: Alpha - 2 Code.
Note: This standard is updated continuously by ISO. Additions/changes to ISO
639-1:1988: Codes for the Representation of Names of Languages are available
on:
http://www.loc.gov/standards/iso639-2/php/code_changes.php
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 8 / 32
[ISO 8583] ISO/IEC 8583. Financial transaction card originated messages — Interchange
message specifications
[ISO 7816-5] ISO/IEC 7816-5. Identification Cards—Integrated Circuit Cards with Contacts—Part
5: Numbering System and Registration Procedure for Application Identifiers
[ISO 18004] ISO/IEC 18004. Information technology—Automatic identification and data capture
techniques—QR Code bar code symbology specification.
[RFC 3966] RFC 3966. The tel URI for Telephone Numbers
[RFC 4648] RFC 4648. The Base16, Base32, and Base64 Data Encodings
1.3.1 Abbreviations
Abbreviation Description
UI User Interface
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 9 / 32
1.3.2 Notations
Value Notation
Representation
'0' to '9' and 'A' to 'F' 16 hexadecimal characters, enclosed in straight quotation marks.
"Test@123" Values that can be represented by the Common Character Set as defined in
[EMV Book 4], enclosed in double straight quotation marks.
For data objects residing in templates, the presence condition for a data object must be
considered in conjunction with the condition of the template in which it resides.
an Alphanumeric data objects contain a single character per byte. The permitted
characters are alphabetic (a to z and A to Z, upper and lower case) and
numeric (0 to 9).
ans Alphanumeric Special data objects contain a single character per byte. The
permitted characters and their coding are shown in the Common Character
Set table in [EMV] Book 4 Annex B.
cn Compressed numeric data objects consist of two numeric digits (having values
in the range Hex '0'–'9') per byte. These data objects are left justified and
padded with trailing hexadecimal 'F's.
n Numeric data objects consist of two numeric digits (having values in the range
Hex '0' – '9') per byte. These digits are right-justified and padded with leading
hexadecimal zeroes. Other specifications sometimes refer to this data format
as Binary Coded Decimal (BCD) or unsigned packed.
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 11 / 32
The following describes the high-level functionality of various components of the QR Code
processing architecture on the consumer device:
• Mobile application/wallet—A consumer-facing user interface (UI) application
provided by the issuer, merchant, or a third-party and provisioned to the consumer’s
mobile device. It includes the functionality to encode the payment credentials based
on this specification, and then displays the resulting QR Code.
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 12 / 32
If supported by the mobile application/wallet, the QR Code may also contain other
consumer opt-in data, for example, for supporting additional services – these
functionalities are not described in this specification.
The mobile application is responsible for providing a UI that will facilitate card
application selection, perform any required CDCVM processing and rendering of the
corresponding QR Code. Figure 2.2 illustrates the process for the consumer.
• QR Code Payload—The payload, consisting of payment token credentials and other
data based on this specification, converted to base64 and encoded in a QR Code.
There are 2 logical components on the merchant device: the QR Code Reader and the POI
Application.
• QR Code Reader—Scans the QR Code, decodes the QR Code and sends the data
recovered to the POI System. This data constitutes the base64 encoded QR Code
Payload.
• POI Application—The application developed by the POI vendor to process the
base64 encoded QR Code payload defined in this specification. Its functions include
base64 decoding, parsing the data, checking content and format and transaction
processing.
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 13 / 32
On the network the following are the roles as per the existing EMV infrastructure:
• Acquirer—The acquirer/processor processing the authorisation transaction received
from the merchant.
• Payment Network—Responsible for transaction routing to the issuer and any
corresponding tokenisation services and functions.
• Issuer—The issuer of the original payment card, that is used in the QR Code
transaction.
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 14 / 32
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 15 / 32
The Payload Format Indicator (tag '85') defines the QR Code format version and is the first
data object of the payload. In this version of the specification, the Payload Format Indicator
has the value "CPV01".
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 16 / 32
The "Additional BER-TLV coded data objects" in templates may include the data objects
listed in Table 6.1. However, the same data objects must not appear in both template '61'
and '62'.
The data objects included in the QR Code Payload should only include those critical for
transaction processing and for the optimal consumer experience.
The following should be taken into consideration when determining the data objects to be
included:
• Although there is no maximum cumulative size for the data objects in the QR Code
Payload, QR Code Readers complying to this specification are only required to
support recovery of 512 bytes of data from the QR Code.
QR Code containing more than 512 bytes of data may not be supported by all QR
Code Readers compliant to this specification. When assessing the cumulative size
and ensuring that it will not exceed 512 bytes, the encoding described in section 3.2
must be taken into account.
• As the cumulative size of the data objects in the QR Code increases, the "QR Code-
in-field" time also increases and the success rate of QR Code reading diminishes.
The "QR Code-in-field" time is the duration in which the cardholder is required to keep
the QR Code in the QR Code Reader's field for a successful read of the QR Code to
occur.
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 17 / 32
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 18 / 32
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 19 / 32
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 20 / 32
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 21 / 32
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 22 / 32
6 Transaction Processing
After the POI has processed the QR Code data payload, it has two sets of data: the POI
Data and the Transparent Data.
The POI uses the POI data for transaction processing and both sets of data to build the
online messages. The POI does not use the Transparent Data for transaction processing.
Transaction processing includes the following:
• Check whether the payment product is supported
• Process Track 2 Equivalent Data (tag '57')
• Display of POI messages
• Print receipt
• Determine format of Transparent Data
• Perform merchant specific processing
Transaction processing is based on the data in Table 6.1 that also indicates requirements for
presence of the data.
Except for the Issuer URL (tag '5F50'), for the definition of these data objects, please refer to
[EMV] Book 3. For the definition of the Issuer URL (tag '5F50'), please refer to Table 6.3.
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 23 / 32
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 24 / 32
Data
Tag Object Format Length Description
'5F50' Issuer URL ans Var. The value of the Issuer URL contains
customer information for electronic receipt
delivery with the syntax defined by a standard
URI scheme.
Supported URI schemes are:
Phone number, defined in [RFC 3966]
Email address, defined in [RFC 6068]
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Page 25 / 32
7 Authorisation
EMV QR Code payment transactions are online authorised.
This specification assumes that:
• Merchants and acquirers support full chip data in order to support EMV QR Code
transactions.
• Issuers (or any processing entity on their behalf) are able to process EMV QR Code
transactions and validate the application cryptogram included in the chip data.
For general guidance on the network message and the data objects, refer to the 'Acquirer
Interface' section and 'Annex C - Example Data Element Conversion' in [EMV] Book 4.
Data objects included in the authorisation message for a QR Code transaction, and the origin
and the values of these data objects, may differ from those for a chip transaction. For
example:
• The Unpredictable Number (UN, tag '9F37') may come from the QR Code and
therefore be card sourced while for a chip transaction it would be terminal sourced.
Mapping of the POI Data and the Transparent Data to an online authorisation request and
the default values requirements are payment system specific and therefore outside of the
scope of this specification. Please contact the respective payment systems for guidance.
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Data Objects Dictionary Page 26 / 32
Application Mnemonic associated with AID according to Refer to Table 6.1 /[EMV] Book 3
Label [ISO 7816-5].
* Special characters limited to
F: ans* space.
T: '50'
L: 1-16
Application PAN Valid cardholder account number. Refer to Table 6.1/[EMV] Book 3
F: cn
T: '5A'
L: var. up to 10
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Data Objects Dictionary Page 27 / 32
Application Contains the application specific data that is Refer to Table 3.1
Specific transparent to the POI App, where the
Transparent application is identified by the ADF name.
Template
F: b
T: '63'
L: var.
Application Contains the application specific data where the Refer to Table 3.1.
Template application is identified by the ADF name.
F: b
T: '61'
L: var.
Application Version number assigned by the payment If this data is absent, the POI
Version Number system for the application. uses '00 10' (version 1.0) as the
default value
F: b
T: '9F08'
L: 2
Common Data Contains the common data that is applicable to Refer to Table 3.1
Template the POI App, for the application(s) in
Application Template(s).
F: b
T: '62'
L: var.
Common Data Contains the common data that is transparent Refer to Table 3.1
Transparent to the POI App, for the application(s) in
Template Application Template(s).
F: b
T: '64'
L: var.
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Data Objects Dictionary Page 28 / 32
Issuer URL Contains customer information for electronic Refer to Table 6.1/identified
receipt delivery with the syntax defined by a below in Table 6.3.
F: ans
standard URI scheme.
Table 6.3
T: '5F50'
L: var.
Last 4 Digits of Represents the last four digits of the underlying Refer to Table 6.1.
PAN PAN affiliated with the Payment Token.
F: n
T: '9F25'
L: 2
Track 2 Contains the data objects of the Track 2 Refer to Table 6.1/Table 6.2
Equivalent Data according to [ISO 7813], excluding start
sentinel, end sentinel, and LRC, as follows:
F: b
Primary Account Number: numeric, var. up
T: '57'
to 19 digits
L: var. up to 19
Field Separator ('D'): binary
Expiration Date (YYMM): numeric, 4 digits
Service Code: numeric, 3 digits
Discretionary Data: numeric, var.
Pad with 'F' if needed to ensure whole
bytes: binary
Payload Format Defines the version of the QR Code. The first 3 "CPV01"
Indicator characters are always “CPV” (Consumer
Presented Version) and the last two characters
F: an
must be decimal digits indicating the version of
T: '85' the payload format.
L: 5
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Data Objects Dictionary Page 29 / 32
Payment Uniquely identifies the PAN to which a payment Refer to Table 6.1
Account token is associated, as defined in [EMV Bulletin
* Permitted characters are
Reference No. 167].
alphabetic upper case and
F: an* numeric.
T: '9F24'
L: 29
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Examples Page 30 / 32
Annex B Examples
This appendix provides examples for converting binary data to and from a QR Code as
defined in this specification.
Note: The data object values provided in the examples below are for illustrative purposes
only and may not be indicative of typical values for each data object.
B.1 Example 1
Binary Data (shown as hex bytes):
85 05 43 50 56 30 31
61 1A
4F 07 A0 00 00 00 55 55 55
57 0F 12 34 56 78 90 12 34 58 D1 91 22 01 12 34 5F
Base64 Data:
hQVDUFYwMWEaTwegAAAAVVVVVw8SNFZ4kBI0WNGRIgESNF8=
QR Code:
B.2 Example 2
Binary Data (shown as hex bytes):
85 05 43 50 56 30 31
61 13
4F 07 A0 00 00 00 55 55 55
50 08 50 72 6F 64 75 63 74 31
61 13
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
®
EMV QR Code Specification for Payment Systems Consumer-Presented Mode
Examples Page 31 / 32
4F 07 A0 00 00 00 66 66 66
50 08 50 72 6F 64 75 63 74 32
62 49
5A 08 12 34 56 78 90 12 34 58
5F 20 0E 43 41 52 44 48 4F 4C 44 45 52 2F 45 4D 56
5F 2D 08 72 75 65 73 64 65 65 6E
64 21
9F 10 07 06 01 0A 03 00 00 00
9F 26 08 58 4F D3 85 FA 23 4B CC
9F 36 02 00 01
9F 37 04 6D 58 EF 13
Base64 Data:
hQVDUFYwMWETTwegAAAAVVVVUAhQcm9kdWN0MWETTwegAAAAZmZmUAhQcm9k
dWN0MmJJWggSNFZ4kBI0WF8gDkNBUkRIT0xERVIvRU1WXy0IcnVlc2RlZW5kIZ8QBwY
BCgMAAACfJghYT9OF+iNLzJ82AgABnzcEbVjvEw==
QR Code:
© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted
®
only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV is a
registered trademark or trademark of EMVCo, LLC in the United States and other countries.
*** END OF DOCUMENT ***