JCB QR Code Payment

Implementation Guide

Version.1.0
May 2018

.
2018 JCB International Co., Ltd. All rights reserved.

All rights regarding this documentation are reserved by JCB Co., Ltd. (“JCB”). This
documentation contains confidential and exclusive information, patents, copyrights, trademarks,
trade secrets, know-how or other intellectual property rights, or any other rights of JCB or JCB
International Co., Ltd. (“JCBI”). You must accept and agree to all of the terms and conditions herein
before viewing, downloading or otherwise using all or any part of this documentation (written,
graphics or otherwise) appearing whether in whole or in part, regardless of form. JCBI is authorized
to conduct JCB’s business outside Japan, and the word of “JCB” in this documentation can be
construed JCB and/or JCBI in each context.

You are prohibited from copying for any third party, distributing, assigning, lending, displaying,
publishing or disclosing or modifying (including but not limited to translating), all or any part of this
documentation (written, graphics or otherwise) appearing whether in whole or in part, regardless of
form, without the prior written permission of JCB.

Certain parts of this documentation are produced by referring to documentations of EMVCo, LLC
(“EMVCo”) and this documentation may contain any information regarding patents, copyrights,
trademarks, trade secrets, know-how or other intellectual property rights, or any other rights of any
third party including EMVCo. Regardless of such reference, JCB makes no representation,
warranty or guarantee expressly nor impliedly whether all or any part of this documentation (written,
graphics or otherwise) appearing whether in whole or in part, regardless of form, does or does not
violate, infringe or otherwise use the information, patents, copyrights, trademarks, trade secrets,
know-how or other intellectual property rights, or any other rights of third parties including EMVCo.
You shall be solely responsible for determining whether your activities require license or permission
from third parties including EMVCo. JCB shall not be liable for your or any third party’s
infringement of any intellectual property rights or any other rights of any third parties including
EMVCo.

While JCB uses reasonable efforts to include accurate and up-to-date information in this
documentation, JCB makes no representation, warranty or guarantee expressly nor impliedly
regarding the accuracy or finality of this documentation (written, graphics or otherwise) appearing
whether in whole or in part, regardless of form and JCB shall not be liable for any product or service
developed or produced in compliance with this documentation. JCB shall assume no liability for
any typographical or other errors or omissions in the content of this documentation (written, graphics
or otherwise) appearing whether in whole or in part, regardless of form. This documentation may
contain links to other sites. JCB is not responsible for the content or practices of such sites.

To the extent permitted by applicable law, in no event JCB, its officers, employees, affiliates, agents,
or contractors, shall be liable to you or any third parties for any damages direct or indirect
consequential, incidental, or punitive damages arising from the use of or inability to use this
documentation, including without limitation, damages for loss of profit, business interruption, loss of
information, damages arising from third party’s claim, even if JCB has been advised of the
possibility of such damages.

QR Code is a registered trademark of DENSO WAVE. It is an ISO 18004- compliant encoding and
visualization of data.

May/2018 © 2018 JCB International All Rights Reserved Page 2

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 Revision History
Item Revision Date Section Contents of Revision
1.0 ALL Initial Issue

May/2018 © 2018 JCB International All Rights Reserved Page 3

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Table of Contents

Table of Contents
1. About This Document ............................................................................................... 7
1.1. Purpose of This Document ................................................................................. 7
1.2. Intended Readers ................................................................................................ 7
1.3. Roles and Responsibilities .................................................................................. 7
1.4. Structure of This Document ............................................................................... 8
1.5. Terminology........................................................................................................ 8
1.6. Revision of This Document ................................................................................ 9
1.7. References .......................................................................................................... 9
2. General Market Practice of QR Code Payment ....................................................... 10
2.1. Overview of QR Code Payment ....................................................................... 10
2.1.1. Business Background for QR Code Payment ............................................ 10
2.1.2. Mode and Type of QR Code Payment ....................................................... 10
2.1.2.1. Merchant Presented Mode ......................................................................11
2.1.2.2. Consumer Presented Mode .................................................................... 13
2.2. Key Benefits of QR Code Payment .................................................................. 14
2.2.1. For Issuers ................................................................................................. 14
2.2.2. For Acquirers ............................................................................................. 14
2.2.3. For Cardmembers ...................................................................................... 14
2.2.4. For Merchants ............................................................................................ 15
2.3. QR Code Payment Use Cases ........................................................................... 16
2.3.1. Face-to-Face Merchant Payment ............................................................... 16
2.3.2. Bill Payment .............................................................................................. 16
2.3.3. E-Commerce Merchant Payment............................................................... 17
3. JCB QR Code Payment Transactions – MPM ......................................................... 18
3.1. Merchant Payment Transaction ........................................................................ 18
3.1.1. Online Processing Flow ................................................................................ 18
3.1.2. Settlement Processing Flow .......................................................................... 19
3.2. System Interface Requirement.......................................................................... 20
3.3. Connectivity Requirement ................................................................................ 21
3.4. Key Items for JCB QR Code Payment Transactions ........................................ 22
3.4.1. EMV Compliant QR Code ............................................................................ 22
3.4.2. Static QR Code and Dynamic QR Code ....................................................... 22

May/2018 © 2018 JCB International All Rights Reserved Page 4

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Table of Contents

3.4.3. QR Code Scanning and Generation .............................................................. 22

3.4.4. Merchant Account Information ..................................................................... 23
3.4.5. Partial Merchant PAN ................................................................................... 23
3.5. Merchant Notification....................................................................................... 23
3.6. Reversal Transaction ........................................................................................ 24
3.7. Crossborder Transaction ................................................................................... 24
3.8. Clearing, Settlement and Reconciliation .......................................................... 24
3.9. Dispute Resolution ........................................................................................... 25
3.10. Risk Management ......................................................................................... 25
3.11. QR Payment Acceptance Mark ..................................................................... 25
4. Issuer Requirements ................................................................................................ 27
4.1. Pre-requisite for Issuer...................................................................................... 27
4.2. Mobile Application Requirement ..................................................................... 27
4.3. QR Code Data Capturing.................................................................................. 28
4.3.1. Capturing of Merchant Account Information................................................ 28
4.3.2. Merchant PAN Recovery .............................................................................. 28
4.4. Cardmember Notification ................................................................................. 28
4.5. Stages in JCB QR Code Payment ..................................................................... 29
4.5.1. Planning Stage............................................................................................... 29
4.5.2. Preparation Stage – Issuer Consideration ..................................................... 29
4.5.3. Implementation Stage ................................................................................... 30
4.5.4. Testing Stage ................................................................................................. 30
4.5.4.1. QR Code Scanning Test (for MPM) .......................................................... 30
4.5.4.2. Sandbox Test for QR Code Payment ......................................................... 31
4.5.4.3. API Test for QR Code Payment................................................................. 31
4.5.4.4. Migration Test and Service Launch ........................................................... 32
4.5.5. Post Launch Stage ......................................................................................... 33
4.5.5.1. Monthly Report from Issuer ...................................................................... 33
5. Acquirer Requirements ............................................................................................ 34
5.1. Pre-requisite for Acquirer ................................................................................. 34
5.2. QR Code Generation and Placement at Merchant ............................................ 34
5.2.1. QR Code Generation ..................................................................................... 34
5.2.2. QR Code Placement at Merchant .................................................................. 34
5.3. Merchant PAN Assignment .............................................................................. 35
5.3.1. Merchant PAN Assignment ........................................................................... 35

May/2018 © 2018 JCB International All Rights Reserved Page 5

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Table of Contents

5.3.2. Partial Merchant PAN Generation ................................................................ 35

5.4. Merchant Notification....................................................................................... 36
5.5. Stages in JCB QR Code Payment ..................................................................... 37
5.5.1. Planning Stage............................................................................................... 37
5.5.2. Preparation Stage – Acquirer Consideration ................................................. 37
5.5.3. Implementation Stage ................................................................................... 38
5.5.4. Testing Stage ................................................................................................. 38
5.5.4.1. QR Code Generation Test (for MPM) ....................................................... 38
5.5.4.2. Sandbox Test for QR Code Payment ......................................................... 39
5.5.4.3. API Test for QR Code Payment................................................................. 40
5.5.4.4. File Import Test for QR Code Payment ..................................................... 40
5.5.4.5. Migration Test and Service Launch ........................................................... 40
5.5.5. Post Launch Stage ......................................................................................... 41
5.5.5.1. Monthly Report from Acquirer .................................................................. 41
Appendix A: Transaction Flows for Standard and Exceptional Processes 42
A-1. Introduction ................................................................................................... 43
A-2. Normal Transaction Flows ............................................................................ 43
A-2-1 Purchase Transaction Flow ........................................................................... 43
A-2-2 Reversal Transaction Flow ............................................................................ 44
A-2-3 Time Out Reversal Transaction Flow ........................................................... 45
A-2-4 Reject Advise Transaction Flow ................................................................... 46
A-2-5 Transaction Status Inquiry Flow ................................................................... 48
A-3 Additional Service Transaction ........................................................................ 49
A-3-1 Exchange Rate Lookup Flow ........................................................................ 49
Appendix B: QR Code Specification for JCB Merchant .................................. 51
Appendix C: Sample of Appendix QR A: Monthly Report Format for QR
Code Payment ............................................................................................................ 54
Appendix D: Sample of Form A (revised for QR) .............................................. 55
Appendix E: Sample of Appendix QR B: AIN Request Form ......................... 56
Appendix F: Self-Test for QR Code Scan and Generation.............................. 57
Appendix G: Sample of Appendix QR C: Test Report for QR Code Scan and
Generation ................................................................................................................... 58

May/2018 © 2018 JCB International All Rights Reserved Page 6

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
1. About This Document

1. About This Document

1.1.Purpose of This Document

The purpose of this document is to provide general information about QR Code

payment as well as the requirements and procedures to implement JCB QR Code
Payment.

Any matter not provided for in this document shall comply with JCBI regulations and
guidelines. Issuers and Acquirers shall also comply with local requirements if any.

1.2.Intended Readers

The intended readers of this document are Issuers and Acquirers who intend to
implement JCB QR Code Payment.

1.3.Roles and Responsibilities

The roles and responsibilities of players involved in JCB QR Code Payment are as
follows.

(a) JCBI

As the brandholder, JCBI is responsible for:

• Defining specifications, policies, regulations and operations for JCB QR Code

Payment.
• Managing JCB QR Code Payment implementation.
• Managing JCB QR Code Payment related test programs.

(b) Issuer

The Issuer is responsible for:

• Complying with the specifications, policies, regulations and operations for JCB
QR Code Payment specified by JCBI.
• Providing a mobile application in an existing mobile banking application or as
a separate application for JCB QR Code Payment.

May/2018 © 2018 JCB International All Rights Reserved Page 7

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
1. About This Document

• Ensuring the security level of the mobile application meets JCBI, regulator, and
its own security policy and standard.

(c) Acquirer

The Acquirer is responsible for:

• Complying with the specifications, policies, regulations and operations for JCB
QR Code Payment specified by JCBI.
• Ensuring that Merchants participating in JCB QR Code Payment fully meet the
merchant qualification standards specified in the JRP and fulfill KYC
requirements specified by local regulations.
• Assigning a unique Merchant PAN (refer to section 5.3) to each Merchant
following JCBI standards, to be used for QR Code generation.
• Ensuring that the participating Merchants are capable of handling JCB QR
Code Payment.

1.4.Structure of This Document

This document is composed of the following chapters:

Section 1 About This document

Section 2 General Market Practice of QR Code Payment
Section 3 JCB QR Code Payment Transactions - Merchant Presented Mode
Section 4 Issuer Requirements
Section 5 Acquirer Requirements
Appendix A: Transaction Flows
Appendix B: Merchant QR Code Specifications for JCB
Appendix C: Sample of Monthly Report Format
Appendix D: Sample of Form A: Project Scope Confirmation Sheet for JCB QR
Code Payment
Appendix E: Sample of Appendix QR B: JCB QR Code Payment API
Configuration
Appendix F: Self-Test for QR Code Generation and Scanning
Appendix G: Sample of Test Report for QR Code Generation and Scanning Test

1.5.Terminology
Shall Denotes a mandatory requirement

May/2018 © 2018 JCB International All Rights Reserved Page 8

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
1. About This Document

Should Denotes a recommendation

May Denotes a possibility or an option

1.6.Revision of This Document

JCBI may revise and reissue this document as necessary. Issuers and Acquirers shall
comply with the contents of the revision. For details such as the effective date of the
revision, please contact JCBI.

1.7.References

References related to this document are as follows:

JCB regulations and specifications:

• JCB Regulatory Publications

• JCB Regulatory Publications for JCB QR Code Payment – MPM
 Note: For details such as the versions of these documents, please contact JCBI.

EMVCo specifications:

• EMV QR Code Specification for Payment Systems (EMV QRCPS), Merchant

Presented Mode
• EMV QR Code Specification for Payment Systems (EMV QRCPS), Consumer
Presented Mode
 Note: For details such as the versions of these documents, please refer to the EMVCo website.

May/2018 © 2018 JCB International All Rights Reserved Page 9

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
2. General Market Practice of QR Code Payment

2. General Market Practice of QR Code Payment

QR Code payment is a fast, secure and inexpensive way for merchants to accept digital
payments from customers, and for customers to purchase items from merchants, without
the trouble of handling cash.

JCBI is joining the growing number of players in the market adopting this faster way of
facilitating payments by using a mobile device for both customer and merchant presented
QR Code payment transactions.

Section 2 introduces the general market practice and standard transaction flows for QR
Code payment. An overview of JCB QR Code Payment and Issuer and Acquirer
requirements are described in Section 3, Section 4 and Section 5.

2.1. Overview of QR Code Payment

2.1.1. Business Background for QR Code Payment
QR Code payments are quickly spreading in the payment industry because of faster
readability and greater storage capacity than standard Universal Product Code barcodes.
They have now become an integral part of the digital payment industry in which more
businesses and consumers all over the world are now using cashless payment transactions
with the rise of mass market affordable smartphones and other mobile devices.

QR Code payments reduce queue times in busy stores and restaurants. Smaller stores just
need to either scan the QR Code on a customer’s mobile phone or display a QR Code to be
scanned by customer’s mobile phone without preparing hardware terminals or an integrated
POS system. In this way, merchants from small businesses such as market stalls and pop up
shops to large scale merchants such as supermarkets, coffee chains, and luxury boutiques
are able to benefit from the convenience of this type of payment.

2.1.2. Mode and Type of QR Code Payment

Per EMVCo standards, QR Code payment transactions are initiated by either Merchant
Presented QR Code or Customer Presented QR Code.

The QR Code can be a static (that is, constant) value for each individual merchant and
customer. Alternatively, it can be dynamic where the transaction specific dynamic data (for

May/2018 © 2018 JCB International All Rights Reserved Page 10

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
2. General Market Practice of QR Code Payment

example, transaction amount and billing information) is combined with the static
information.

2.1.2.1. Merchant Presented Mode

Merchant Presented QR Code Payment Mode transaction (MPM transaction) enables
customers to make purchases using a merchant displayed QR Code that includes merchant
information.

MPM transactions give more flexibility for customers to pay without waiting in a queue.

Also, from the merchant acquiring side, it takes minimum infrastructure setup to capture
payments by receiving payment confirmation through the customer’s own mobile. Figure
2.1.2.1-1 describes the general transaction flow of MPM transaction.

Figure2.1.2.1-1 QR Code Capture and Processing Flow for MPM Transaction

# Description
1 The Cardmember opens a mobile application that has the capability to scan the
QR Code displayed at the merchant and initiates a payment transaction.
*The mobile application may be a part of existing mobile banking application offered by the

May/2018 © 2018 JCB International All Rights Reserved Page 11

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
2. General Market Practice of QR Code Payment

Issuer or a third party.

2 The Issuer receives the transaction and secures or withdraws the transaction
amount from the Cardmember’s account.
3 The Issuer forwards the transaction to the payment network.
4 The payment network forwards the transaction to the Acquirer.
5 Upon receiving the transaction, the Acquirer checks the validity of the
Merchant Account Information as well as other merchant credentials and,
when valid, credits the transaction amount to the account associated with the
Merchant Account Information. The Acquirer sends a response back to the
payment network.
6 The Merchant awaits notification of a successful transaction before delivering
the goods and services to the Cardmember.
7 The payment network forwards the transaction response back to the Issuer.
8 The Issuer also provides a notification to the Cardmember (typically through
the mobile application).

The following is the simple example of steps of the Cardmember doing an MPM
transaction.

 Note: 2FA – Two Factor Authentication

May/2018 © 2018 JCB International All Rights Reserved Page 12

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
2. General Market Practice of QR Code Payment

2.1.2.2. Consumer Presented Mode

In Consumer Presented QR Code Mode transaction (CPM transaction), the Cardmember is
able to make purchases using credentials associated with their card and previously
provisioned to their device by selecting the QR option for payment within their mobile
application, which will result in the display of a QR Code, and having that QR Code
scanned at the time of payment to complete the transaction.
These transactions (which are traditional card payments) are basically authorized online
and given that the scanning of the QR Code is a one-way transfer of data from the
Cardmember’s device to the Point of Interaction (POI), the payload of the QR Code does
not contain any data from the POI.
Figure 2.1.2.2-1 below describes the general transaction flow of CPM transaction.
 Note: CPM transactions are not supported by JCBI at this time.

Figure2.1.2.2-1 QR Code Capture and Processing Flow for CPM Transaction

# Description
1&2 The Merchant captures the Cardmember’s QR Code using the merchant
system and sends the information to the Acquirer in the same way as a
traditional card payment transaction.
3 The Acquirer validates the Merchant’s status and forwards the transaction to
the payment network.
4 The payment network forwards the transaction to the Issuer.
5 The Issuer checks the validity of the Cardmember account and other
credentials and when valid, debits the transaction amount from the
Cardmember account. The Issuer sends an authorization response back to
the payment network.
6&7 The payment network forwards the response back to the Acquirer. The
Acquirer forwards the response back to the Merchant.

May/2018 © 2018 JCB International All Rights Reserved Page 13

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
2. General Market Practice of QR Code Payment

2.2. Key Benefits of QR Code Payment

2.2.1. For Issuers
 Customer base growth – Issuers will be able to acquire more Cardmembers who
prefer an easy and convenient payment solution.
 Positive brand impact – Issuers can differentiate themselves as innovative and
customer focused.
 Digital payment – Issuers can make a shift from cash payment to digital payment.
 Revenue – Issuers can grow revenue by increasing transaction volume through
payments using QR Code.

2.2.2. For Acquirers

 Customer base growth – Acquirers will be able to provide payment solutions to
Merchants that could not afford to accept non-cash payment before. Acquirers can
support Merchants with zero or very low setup cost to implement QR Code
payments.
 Positive brand impact – Acquirers can differentiate themselves as innovative and
merchant focused.
 Digital payment – Acquirers can promote a shift from cash payment to digital
payment.
 Revenue – Acquirer can grow revenue by increasing transaction volume through
payments using QR Code.

2.2.3. For Cardmembers

 Convenience – Cardmembers can use their own mobile device to make payment.
All transaction information can be stored in the mobile application for MPM
transactions in the mobile device.
 Simplicity - Cardmembers do not need to take out a plastic card from their wallet or
to enter a card number for each payment, instead, Cardmembers just need to open
the mobile application to make a payment.
 Availability – As QR Code payment transaction is very easy for Merchants to
implement, Cardmembers will be able to pay more small merchants that could only
accept cash before.
 Security – The transaction is more secure with added mobile security features.
Additionally, there will be no card information that is passed and stored at the
merchant (this applies only to MPM).

May/2018 © 2018 JCB International All Rights Reserved Page 14

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
2. General Market Practice of QR Code Payment

2.2.4. For Merchants

 Convenience and simplicity – QR Code payment is very easy to setup to accept
digital payment. All that that the Merchant needs for MPM transaction is a QR Code
sticker. For CPM transaction, the Merchant scans the presented QR Code with a
reader. The Merchant does not need to swipe, insert, or ask the Cardmember to tap
the card on the terminal.
 Low setup cost – Merchants only need a device to receive notifications from the
Acquirer. Traditional POS devices are not needed (this applies only to MPM).
 Revenue – Adding QR payment as a convenient payment can drive up sales and
revenue.

May/2018 © 2018 JCB International All Rights Reserved Page 15

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
2. General Market Practice of QR Code Payment

2.3. QR Code Payment Use Cases

This section describes some examples of use cases for QR Code payment for MPM. Use
cases for CPM are the same as traditional card payments and therefore are not introduced in
this document. These use cases are standard examples which are widely and commonly
used in the market.

2.3.1. Face-to-Face Merchant Payment

1. The Cardmember purchases goods and services at a physical Merchant location.

2. The Cardmember scans the QR Code displayed at the Merchant.
3. The Cardmember enters the transaction amount into the mobile application when
prompted and performs any required Cardholder Verification Method (CVM) for
Cardmember authentication.
*The Cardmember may need to enter a tip or convenience fee if prompted.
*Examples of CVM are PIN, one time password, fingerprint, and face recognition.
4. The Merchant receives a notification from the Acquirer that the transaction is
approved or declined.
5. The Cardmember receives a payment confirmation from the Issuer in their mobile
application or via SMS and receives the goods and services from the Merchant.

2.3.2. Bill Payment

1. The Cardmember receives a bill that shows a QR Code (Dynamic QR Code is

recommended for bill payment).
2. The Cardmember scans the QR Code from the bill with their mobile application.

May/2018 © 2018 JCB International All Rights Reserved Page 16

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
2. General Market Practice of QR Code Payment

3. The Cardmember enters the transaction amount when prompted on the display and
then performs any required CVM for Cardmember authentication.
*The Cardmember may need to enter a tip or convenience fees if prompted.
4. The Merchant (for example, the billing server) receives Merchant Notification from
the Acquirer that the transaction is approved or declined.
5. The Cardmember receives a payment confirmation from the Issuer on their mobile
application or via SMS.

2.3.3. E-Commerce Merchant Payment

1. The Cardmember purchases goods and services from a Merchant on the internet.
2. The Cardmember scans the QR Code displayed on the screen (Dynamic QR Code
customized for each transaction is recommended for e-commerce Merchant
payment).
3. The Cardmember enters the transaction amount into the mobile application when
prompted and performs any required CVM for Cardmember authentication.
*The Cardmember may need to enter a tip or convenience fees if prompted.
4. The Merchant receives notification from the Acquirer that the transaction is
approved or declined.
5. The Cardmember receives a payment confirmation from the Issuer on their mobile
application or via SMS.
6. The Merchant delivers the goods and services to the Cardmember.

May/2018 © 2018 JCB International All Rights Reserved Page 17

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
3. JCB QR Code Payment Transactions -MPM-

3. JCB QR Code Payment Transactions – MPM

In accordance with emerging market needs, JCBI is rolling out QR Code payment, starting
with MPM transaction.

This section explains the JCB QR Code Payment transaction flows for MPM transaction
from the perspective of authorization and settlement. It also gives an overview of JCB API
based MPM transactions in a single message environment.

3.1. Merchant Payment Transaction

3.1.1. Online Processing Flow

JCBI expanded its existing online processing to include authorization processing for JCB
QR Code Payments. Licensees should use single message API connectivity for JCB QR
Code Payments. The online interface between Licensees and JCBI is the JCB Authorization
System Interface for QR (Authorization System for QR).

Figure3.1.1-1 Processing Flow for JCB QR Code Payment

May/2018 © 2018 JCB International All Rights Reserved Page 18

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
3. JCB QR Code Payment Transactions -MPM-

# Description

0 The Cardmember opens the mobile application using the authentication required
by the Issuer.

1 The Cardmember scans the QR Code displayed by the Merchant, performs the
required CVM and enters the transaction amount (if required).
*Examples of CVM are PIN, one time password, fingerprint, and face recognition.
The Mobile Application sends the transaction to the Issuer for validation.

2 The Issuer validates the Cardmember’s credential and secures or debits the funds
for payment.
*The Issuer recovers a Partial Merchant PAN to the full 16-digit Merchant PAN before
forwarding the payment request to JCBI. Please refer to Section 5.3.1 for further details.
*The Issuer may convert the transaction amount to the Cardmember billing currency if
necessary before securing or debiting the funds from the account.

3&4 The Issuer forwards the transaction to JCBI (Authorization System for QR) and
JCBI forwards the transaction to the Acquirer.

5 The Acquirer validates the Merchant’s status, populates the Local Transaction
Date and Time upon validation and sends an approval response back to JCBI.

6 The Acquirer sends Merchant Notification of a successful payment to the

Merchant.

7 JCBI forwards the transaction response back to the Issuer.

8 The Issuer provides notification to the Cardmember of successful payment via

the mobile application, SMS, or other method agreed with the Cardmember.

*The numbers in this figure correspond to the numbers in Figure 3.1.1-1.

If JCBI sends a transaction response that the transaction failed (that is, rejected due to JCBI
validation or Acquirer rejection), the Issuer reverses the payment from the Cardmember’s
account and provides notification to the Cardmember that the payment failed.

3.1.2. Settlement Processing Flow

Settlement processing for JCB QR Code Payment is slightly different from traditional card
payments. Licensees receive reconciliation data via Batch Interface message (variable
format).

Incoming Interchange File and Outgoing Interchange File for QR Code payment are not
generated for QR Code Payments since the transactions are processed using a single

May/2018 © 2018 JCB International All Rights Reserved Page 19

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
3. JCB QR Code Payment Transactions -MPM-

message. JCBI provides Settlement Reports and settlement results files which contain
reconciliation data to Licensees for their settlement and reconciliation processes.

All files are exchanged between Licensees and JCBI using the existing procedure through
either Web-EDI or GXS-EDI.

# Description

9 JCBI Settlement System cut-off daily for approved transactions.

*Please refer to Operations Manual for QR Code Payment for details.

10 Licensees receive Settlement Reports and reconciliation data on the day of the
cut-off.

11 JCBI and Licensees complete settlement by agreed method by both parties.

*The numbers in this figure correspond to the numbers in Figure 3.1.1-1.

3.2. System Interface Requirement

Authorization System for QR is a single worldwide gateway provided by JCBI to all

Licensees who use public APIs for JCB QR Code Payment.

Licensee shall set up the system interface with the Authorization System for QR in the
following manner:

• API based Interface – Licensees send and receive API messages to and from the
Authorization System for QR.

• Single Message – JCB QR Code Payment is only available as single message

processing.

JCBI provides a set of APIs to Licensees in order to execute JCB QR Code Payment, along
with technical instruction documentation.

Licensee systems shall use the API codes provided by JCBI to send JCB QR Code Payment
transactions and receive transaction responses. Licensees shall follow JCBI message
specifications.

Figure3.2-1 API MPM Transaction Flow

May/2018 © 2018 JCB International All Rights Reserved Page 20

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
3. JCB QR Code Payment Transactions -MPM-

Licensees receive Settlement Report and settlement results files which includes
reconciliation data via Batch Interface message (variable format).

 For details of the API specification, please refer to JCB Regulatory Publications – System Specifications
– Online Interface Guide for QR Code Payment.

 For details of the batch interface message specification in variable format, please refer to JCB
Regulatory Publications – System Specifications – Batch Interface Guide for QR Code Payment.

3.3. Connectivity Requirement

Licensees shall establish system connectivity with the Authorization System for QR in the
following manner:

 Use a secure Internet connection. The network bandwidth is no less than 64Kbps. If
requested by JCBI, Licensees shall upgrade bandwidth to ensure smooth online
transaction processing.

 Use the API codes provided by JCBI in their host system program to format
messages.

 Connect to the IP addresses designated by JCBI to establish connectivity to the

Authorization System for QR.

 Design an infrastructure and network communication failover plan (that is, a BCP
plan) to eliminate the risk of single point of failure at the network communication
level.

May/2018 © 2018 JCB International All Rights Reserved Page 21

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
3. JCB QR Code Payment Transactions -MPM-

3.4. Key Items for JCB QR Code Payment Transactions

3.4.1. EMV Compliant QR Code

EMV compliant QR Code is capable of storing multiple payment network information

within a single QR Code, which helps the Merchant avoid displaying multiple QR Codes,
and helps Cardmembers avoid scanning the wrong QR Code. JCB QR Code specifications
(Appendix B) are compliant with EMVCo specifications.

3.4.2. Static QR Code and Dynamic QR Code

JCB QR Code Payment supports both Static QR Code and Dynamic QR Code. Acquirers
shall choose the appropriate type depending on the Merchant’s business and transaction
characteristics:

1. Static – The information in the QR Code does not change. After the QR Code has
been generated and printed, the content is fixed.

2. Dynamic – The information in the QR Code may be changed per transaction to

store more information such as bill number and transaction amount, which reduces
manual input. Dynamic QR Code should be generated by the Merchant’s
application and displayed on the Merchant’s terminal or computer screen.

3.4.3. QR Code Scanning and Generation

The Issuer shall design a Mobile Application that can scan QR Codes. The Issuer shall
forward the necessary data to JCBI in accordance with the JCB QR Code Payment message
specification.

The Acquirer shall generate QR Codes to be displayed at the Merchant based on EMVCo
standards and Appendix B, which include a Merchant PAN starting with the Acquirer
Identification Number (AIN) assigned by JCBI for JCB QR Code Payment.

Licensees shall perform self-tests to ensure the quality of scanning and generating QR
Codes as described in Appendix F.

JCBI may introduce a certification program to evaluate the Issuer’s Mobile Application and
Acquirer’s QR Code generation in the future.

May/2018 © 2018 JCB International All Rights Reserved Page 22

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
3. JCB QR Code Payment Transactions -MPM-

 Please refer to Appendix B and EMVCo specifications for the details of QR Code specifications.

3.4.4. Merchant Account Information

Merchant Account Information is stored in EMV compliant QR Codes. The format and
values are unique per payment network and therefore several values may be stored in the
QR Code when the Merchant accepts cards from multiple payment networks.

Merchant Account Information with IDs 13 and 14 is reserved for JCB by EMVCo and is
the indicator for the Issuer to route the transaction to JCBI. Merchant Account Information
stored under ID “13” and “14” is either Merchant PAN or Partial Merchant PAN as
specified in Appendix B.

3.4.5. Partial Merchant PAN

A Partial Merchant PAN is derived from the Merchant PAN, which is a 16-digit unique ID
that identifies a Merchant that accepts JCB QR Code Payment.

The Merchant PAN may include consecutive zeroes after the Acquirer Identification
Number (AIN). In this case, a Partial Merchant PAN should be stored in Merchant Account
Information IDs 13 and/or “ 14 to optimize manual entry.

If the Mobile Application fails to properly scan the QR Code displayed at the Merchant, the
Cardmember needs to manually enter merchant information in their Mobile Application.
The detailed layouts of Merchant PAN and Partial Merchant PAN are described in Section
5.3.

3.5. Merchant Notification

Merchant Notification is used by the Merchant to confirm the transaction results (that is,
approved or declined) and to decide whether to provide goods and services to the
Cardmember.

The Acquirer shall send Merchant Notifications via the merchant application, SMS, or
other means agreed between the Acquirer and the Merchant. Detailed requirements for
Acquirers are described in Section 5.4.

May/2018 © 2018 JCB International All Rights Reserved Page 23

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
3. JCB QR Code Payment Transactions -MPM-

3.6. Reversal Transaction

For MPM transactions, the Issuer initiates the Purchase transaction. Reversals are initiated
only by the Acquirer when required due to a failure of the transaction.

The Acquirer identifies the original Purchase transaction when initiating a Reversal. The
Acquirer shall set the OriginatorReferenceNumber in the message to indicate which
Purchase transaction is to be reversed.

3.7. Crossborder Transaction

A crossborder transaction is a transaction with a Transaction Country Code that is different

from the Issuer Country Code.

For traditional card payments, the Acquirer provides the transaction amount and currency
code, and the Issuer converts the transaction amount to the Cardmember billing currency.
For MPM transactions, the Issuer receives the transaction first, so that the transaction
currency amount is converted by the Issuer.

Issuers may use the Exchange Rate Lookup API to get the converted amount from JCBI.
JCBI responds the exchange rate and the converted amount in the Cardmember billing
currency or Issuer settlement currency based on data (the original transaction amount, the
transaction currency code, and the target currency code) sent via the API.

JCBI also provides the settlement amount in the settlement currency agreed with the
Licensee during the onboarding process.

 Note: Crossboarder transaction is not supported by JCBI as of February 2018. Licensees who wish to
implement crossborder transaction need to contact JCBI for further information.

3.8. Clearing, Settlement and Reconciliation

Since the transactions are processed as single message, JCBI does clearing using the
successful transaction logs tanked in the Authorization System for QR on the day. The
clearing data is then used to do settlement between JCBI and Licensees. JCBI provides
Settlement Report and settlement results files including reconciliation data through the
batch file transfer system.

May/2018 © 2018 JCB International All Rights Reserved Page 24

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
3. JCB QR Code Payment Transactions -MPM-

Unlike the traditional card payment process, Acquirers shall not send any Outgoing
Interchange File to JCBI for MPM transactions, including Reversal and Refund.

For crossborder transactions, there will be no recalculation of the amount during the
clearing process. The settlement amount in settlement currency is calculated at the time of
the online message processing through API.
 Note: Crossborder transaction is not supported by JCBI as of February 2018. Please contact your JCBI
representative for further information.

 For the details of batch file specifications, please refer to JCB Regulatory Publications, System
Specifications – Batch Interface Guide for QR Code Payment.

3.9. Dispute Resolution

For dispute transactions such as Retrieval Request and Chargebacks, JCB Operations
Support shall be used by Licensees in the same way as the traditional card payment
process.
The chargeback reason codes available for JCB QR Code Payment are defined in the JRP

 For details of the dispute process, please refer to JCB Regulatory Publications for QR Code Payment -
Regulations Section 7.

3.10. Risk Management

Risk management requirements such as transaction velocity limits for QR Code
transactions may be specified in the JCB Regulatory Publications when applicable.
Licensees shall comply with any requirements specified by the government body or
regulator in their country.

 For details of risk management requirements, please refer to JCB Regulatory Publications for QR Code
Payment- Regulations Section 3.2 and 4.5.

3.11. QR Payment Acceptance Mark

The EMV® QR Payment Mark specified by EMVCo shall be used together with the JCB
Emblem to notify acceptance of JCB QR Code Payment.

May/2018 © 2018 JCB International All Rights Reserved Page 25

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
3. JCB QR Code Payment Transactions -MPM-

JCB Emblem EMV® QR Payment Mark

Licensees should refer to the JCB VI Design Manual for JCB Emblem requirements. The
digital data shall be downloaded from the following website:
http://www.jcb.co.jp/bdmanual/en/basicDesignElements/jcbEmblem/index01download01.html

 For details of the JCB Emblem, please refer to JCB Regulatory Publications – Schedule D.

 For the detailed and up-to-date requirements of the EMV® QR Payment Mark, please refer to the
EMVCo website (https://www.emvco.com/about/trademark-centre/).

 Note: EMV® is a registered trademark or trademark of EMVCo LLC in the United States and other
countries.
 Note: The QR Payment Mark, consisting of a stylized QR code, is a trademark owned by and used with
permission of EMVCo, LLC.

May/2018 © 2018 JCB International All Rights Reserved Page 26

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed to
any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
4. Issuer Requirements

4. Issuer Requirements
This section describes the requirements for Issuers to implement JCB QR Code
Payment, in addition to the requirements specified in the JCB Regulatory Publications
for traditional card payment.

4.1.Pre-requisite for Issuer

Issuers shall conclude a License Agreement for Issuing with JCBI.

4.2. Mobile Application Requirement

Issuers may design and develop their own mobile application, which must meet the
following requirements:
 The Issuer shall provide the mobile application to Cardmembers in its existing
mobile banking application or as a separate application.
 The mobile application shall be able to authenticate the Cardmember with at
least two factor authentication (for example, PIN, one time password, fingerprint,
or face recognition).
 The mobile application shall be able to scan the QR Code displayed at the
Merchant and parse it according to Appendix B and EMVCo specifications.
*The mobile application may verify the Merchant PAN and CRC before allowing the user to
enter the transaction amount.
 The mobile application shall be able to connect to the Issuer system in a secure
manner and then send the transaction to the Authorization System for QR.
 The mobile application shall be able to clearly display Merchant information
(for example, merchant name, merchant city, and merchant type) in order for the
Cardmember to identify whether the scanned QR Code is correct.
 The mobile application shall be able to prompt entry of the transaction amount
and transaction currency code.
 The mobile application shall display any additional information to the
Cardmember as needed.
 The mobile application should allow the Cardmember to confirm the amount
before sending the transaction to the Issuer.
 The mobile application should allow the Cardmember to check the status of the
transaction after the transaction is sent.
 Note: JCB may introduce certification of mobile applications in the future.

May/2018 © 2018 JCB International All Rights Reserved Page 27

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
4. Issuer Requirements

4.3. QR Code Data Capturing

4.3.1. Capturing of Merchant Account Information

The Issuer shall recognize the Merchant Account Information ID 13 and 14 stored in the
QR Code as JCB QR Merchant information and shall route the transactions to JCBI
accordingly.

4.3.2. Merchant PAN Recovery

A Partial Merchant PAN may be stored in the QR Code as described in Section 3.4.5. If
so, the Issuer shall populate the eliminated zeros to recover the 16-digit Merchant PAN
before forwarding the transaction to JCBI.

4.4. Cardmember Notification

The Issuer shall send Cardmember Notification to the Cardmember to inform them of
the transaction result via SMS, the mobile application or any other method agreed
between the Issuer and Cardmember agreed during the QR Code payment registration
process.

The Issuer should provide at least the information below to the Cardmember, in
consideration of Reversal, Chargeback, or Transaction Status Inquiry.

 Transaction Local Date and Time (received from the Acquirer)

 Authorization Results (approved or declined)

 Approval Code

 Merchant PAN and Merchant Name

 Transaction Amount
 Transaction Currency Code (3-digit numeric value defined by ISO 4217)

 System Trace Audit Number (value assigned by the Issuer to identify the
transaction for Reversal)

 Bill Number/Invoice Number (if captured from QR Code)

May/2018 © 2018 JCB International All Rights Reserved Page 28

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
4. Issuer Requirements

4.5. Stages in JCB QR Code Payment

4.5.1. Planning Stage

At the planning stage, the Issuer shall:

 Contact its JCBI representative to launch the QR Code implementation project.

 Submit Form QR A: Project Scope Confirmation Sheet for JCB QR Code
Payment, Form QR B: JCB QR Code Payment API Configuration and any other
required documents to JCBI.
 Agree to the Project Plan.
 For details of Form A, please refer to Appendix D and JCB Regulatory Publications for QR Code
Payment – Forms.

 For details of Appendix QR B, please refer to Appendix E and JCB Regulatory Publications –
Operations Manual for QR Code Payment.

4.5.2. Preparation Stage – Issuer Consideration

At the preparation stage, the Issuer shall consider:

 Selection of a mobile application vendor and application design (including

registration and transaction process, terms and conditions for Cardmembers,
supporting services (for example, transaction status inquiry, online chargeback
function, and transaction history page) and user interface layouts).
 Host system design based on the JCB Regulatory Publications and system
specifications
 Sandbox preparation (for example, create a project in the sandbox and test keys
app) by submitting the forms requested by JCBI.
 Card artwork in the mobile application. The Issuer shall request card artwork
approval when new artwork or revised artwork is to be displayed on the mobile
application.
 IIN management.
 Note: The Issuer should use the same IIN already assigned for traditional card payments. If
an additional IIN is necessary, please contact your JCBI representative.
 CVM management for QR Code Payment (for example, PIN, one time password,
fingerprint, and face recognition).
May/2018 © 2018 JCB International All Rights Reserved Page 29
NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
4. Issuer Requirements

 Settlement and reconciliation processes.

 Cardmember inquiry support and dispute support team operations.
 Risk management.

4.5.3. Implementation Stage

At the implementation stage, the Issuer shall complete:

 Development and debugging of the authorization system.

 Development and validation of the mobile application against the Issuer’s
mobile application service level and security requirements.
 Issuers who do not yet support single message processing shall develop their settlement host
system to be capable of clearing and settlement without receiving Incoming Interchange Files from
JCBI.

 For details of authorization system requirements, please refer to JCB Regulatory Publications –
System Specifications – Online Interface Guide for QR Code Payment.

4.5.4. Testing Stage

At the testing stage, the Issuer shall complete a QR Code Scanning Test, Sandbox Test
(self-test in the Sandbox Test environment) and API Test for QR Code Payment in the
interaction environment.

The API Test is an interactive test between the Issuer and JCBI. The Issuer shall request
its JCBI representative to arrange the test schedule.

4.5.4.1. QR Code Scanning Test (for MPM)

The purpose of this test is to ensure that the mobile application properly scans QR
Codes. This is a self-test by the Issuer.

 The Issuer shall perform a self-test of its mobile application to ensure that Static
and Dynamic QR Code scanning works properly. Test cases and criteria are
described in Appendix F.

 The Issuer shall submit the Test Report (Appendix G) to JCBI for confirmation.

May/2018 © 2018 JCB International All Rights Reserved Page 30

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
4. Issuer Requirements

4.5.4.2. Sandbox Test for QR Code Payment

The purpose of this test is to validate that API messages are correctly generated by the
Issuer’s authorization host in accordance with JCB Regulatory Publications - System
Specifications – Online Interface Guide for QR Code Payment. This test is a self-test
performed by the Issuer in the Authorization System for QR test environment. This test
may be used for debugging purposes as well.

The successful completion of the Sandbox Test is the criteria to proceed to the API Test
in the interaction environment.

 JCBI provides the Sandbox Test environment for Licensees to perform

self-debugging.
 JCBI provides the technical implementation details, which includes the details of
the test cases to be executed and the procedure for executing the self-test.
 JCBI prepares client and server security test certificates and distributes them to
the Issuer.
 JCBI configures the IP address white listing in the Sandbox Test environment
allowing the Issuer to perform the Sandbox Test.
 The Issuer shall make a secured connection to the Sandbox Test environment
that simulates the Acquirer when executing the test cases.
 The Issuer shall submit the test results captured during the self-test to JCBI for
validation.

A batch interface test (including exchange of settlement summary data, reconciliation

data, and other batch files) is out of scope of the Sandbox Test. The same process as for
traditional card payments shall apply. If the Issuer supports new functions, changes the
file transfer method, or changes any other operational procedure when implementing
JCB QR Code Payment, JCBI may request the Issuer to perform additional tests which
are not specified in this document.

4.5.4.3. API Test for QR Code Payment

The purpose of this test is to validate that API messages are correctly generated by the
Issuer’s authorization host in accordance with the JCB Regulatory Publications -
System Specifications – Online Interface Guide for QR Code Payment.
May/2018 © 2018 JCB International All Rights Reserved Page 31
NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
4. Issuer Requirements

As this test is an interactive test with JCBI, the Issuer shall request its JCBI
representative to arrange the test schedule.

The successful completion of the API Test is the criteria to proceed to the Migration
Test.

 Upon the successful completion of the Sandbox Test, JCBI shall provide the
schedule for the API Test.
 The Issuer shall connect to the Authorization System for QR test environment
and execute the online test cases with JCBI.

If the Issuer supports new functions, changes the file transfer method, or changes any
other operational procedure when implementing QR Code Payment, JCBI may request
the Issuer to perform additional tests which are not specified in this document.

4.5.4.4. Migration Test and Service Launch

The purpose of this test is to ensure that the Issuer is ready to go live and release JCB
QR Code Payment to Cardmembers.

The Migration Test shall be completed when both parties confirm that all the test
transactions specified by JCBI are successful in the production environment, which
includes online API connectivity as well as batch file exchange and data import.

 Upon successful completion of the API Test, the Issuer shall agree with JCBI on
the Migration Plan and other preparation required before the first transaction.
 The Issuer shall receive a Live Operation Reference (LOR) for QR Code
Payment from JCBI as the service guide for system related operations (including
system maintenance procedures and emergency procedures).

May/2018 © 2018 JCB International All Rights Reserved Page 32

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
4. Issuer Requirements

4.5.5. Post Launch Stage

4.5.5.1. Monthly Report from Issuer

The Issuer shall submit a Monthly Report for JCB QR Code Payment to JCBI within the
first 10 business days of every month. The Monthly Report format is provided in
Appendix C.

May/2018 © 2018 JCB International All Rights Reserved Page 33

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
5. Acquirer Requirements

5. Acquirer Requirements
This section describes the requirements for Acquirers to implement JCB QR Code
Payment, in addition to the requirements specified in the JCB Regulatory Publications
for traditional card payment.

5.1.Pre-requisite for Acquirer

Acquirers shall conclude a License Agreement for Acquiring with JCBI.

5.2. QR Code Generation and Placement at Merchant

5.2.1. QR Code Generation

The Acquirer shall generate QR Codes according to EMVCo specifications and
Appendix B. Acquirers shall ensure that the quality and size are appropriate for easy
scanning by the Cardmember’s mobile application. The Merchant PAN or Partial
Merchant PAN should be printed below the QR Code displayed at the Merchant for
manual entry.

The Acquirer shall provide the QR Code to the Merchant by email, a webpage for
Merchant use, via the merchant application, or by other means. The Acquirer shall
ensure that the Merchant keeps the QR Code (whether printed or displayed) in scanable
condition.

The Acquirer shall re-generate and replace the QR Code when Merchant Account
Information is changed for any reason.

The maximum size is 3.5 cm width X height when using 0.5 mm square dots.
*Acquirers should not use a QR Code with X-dimension smaller than 0.5 mm due to possible
problems in printing and scanning.

5.2.2. QR Code Placement at Merchant

The Acquirer shall ensure that:

May/2018 © 2018 JCB International All Rights Reserved Page 34

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
5. Acquirer Requirements

• Merchants display the QR Code where it is easily scanable by Cardmembers using

their mobile application.
• The Merchant Notification receiving device is correctly linked to the displayed QR
Code, especially if there are multiple payment lanes.

5.3. Merchant PAN Assignment

5.3.1. Merchant PAN Assignment

JCBI assigns a new Licensee ID and an 8-digit Acquirer Identification Number (AIN) to
the Acquirer to be used for identifying Merchants that accept JCB QR Code Payment.
Acquirers shall generate a Merchant PAN for each Merchant by concatenating its AIN
with a unique 7-digit number, followed by a Check Digit. The unique 7-digit number
should be padded with leading zeros.

Example:
Merchant PAN: 3158 0000 0000 012x

Acquirer Identification Number for Acquirer: 31580000 (1st -8th digit)

Unique number for each merchant: 0000012 (9th-15th digit)

Check Digit: x (16th digit)

3 1 5 8 0 0 0 0 0 0 0 0 0 1 2 x

Assigned BIN to Acqurier X Unique Number for each Merchant Check Digit
(Luhn Formula)

5.3.2. Partial Merchant PAN Generation

The Acquirer should use a Partial Merchant PAN and populate into the QR Code by
eliminating the leading zeros of the unique number for each Merchant. The Partial
Merchant PAN is convenient and helps avoid errors when Cardmembers manually enter
the merchant account information in their mobile application.

May/2018 © 2018 JCB International All Rights Reserved Page 35

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
5. Acquirer Requirements

Partial Merchant PAN: 3158 0000 12 x

3 1 5 8 0 0 0 0 1 2 x

Assigned BIN to Acqurier X Unique Number Check Digit

for each Merchant

The Merchant PAN or Partial Merchant PAN should be displayed together with the QR
Code at the Merchant for Cardmembers to enter if the mobile application fails to scan
the QR Code properly. When a Partial Merchant PAN is stored in the QR Code, it shall
be recovered by the Issuer to the 16-digit Merchant PAN.

5.4. Merchant Notification

The Acquirer shall send a Merchant Notification to the Merchant of the transaction
result via SMS, the merchant application, or any other method agreed between the
Acquirer and the Merchant.

The Acquirer shall ensure that the notification is appropriately linked to the QR Code
displayed at the Merchant, especially if there are multiple payment lanes (for example,
by assigning a Merchant PAN to each lane, or utilizing the Terminal ID as an identifier).

The Acquirer should provide at least the information below to Merchants, but not
limited to, in consideration of Reversal.

 Transaction Local Date and Time

 Authorization Results (approved or declined)

 Approval Code

 Merchant PAN and Merchant Name

 Transaction Amount
 Transaction Currency Code (3-digit numeric value defined by ISO 4217)

 Cardmember Name
 System Trace Audit Number (value assigned by the Issuer to identify the
transaction for Reversal)

 Bill Number/Invoice Number (if delivered to the Acquirer)

May/2018 © 2018 JCB International All Rights Reserved Page 36

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
5. Acquirer Requirements

5.5. Stages in JCB QR Code Payment

5.5.1. Planning Stage

At the planning stage, the Acquirer shall:

 Contact its JCBI representative.

 Submit Form A (Appendix D), Form QR B (Appendix E), and any other
required documents to JCBI.

 Agree to the Project Plan.

 For details of Form A, please refer to Appendix D and JCB Regulatory Publications for QR Code
Payment – Forms.

 For details of the Appendix QR B, please refer to Appendix F and JCB Regulatory Publications –
Operations Manual.

5.5.2. Preparation Stage – Acquirer Consideration

At the preparation stage, the Acquirer shall consider:

 Selection of a merchant application vendor or Acquirer website developer and

application design (including Merchant on-boarding process, terms and
conditions for Merchants, supporting services (for example, transaction status
inquiry and online reversal functions) and user interface layouts).
 Host system design based on the JCB Regulatory Publications and system
specifications.
 Sandbox preparation (for example, create a project in sandbox and test keys
app).
 AIN management and Merchant PAN assignment
 Note:The Acquirer shall apply for a new LCID and receive an AIN for merchant
management. Please contact your JCBI representative.
 Merchant Notification account management
 Note: If the merchant has multiple payment lanes, the Acquirer shall ensure that
notification is delivered to the correct lane.
 Settlement and reconciliation processes.
 Merchant inquiry support and dispute team operations.

May/2018 © 2018 JCB International All Rights Reserved Page 37

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
5. Acquirer Requirements

 Risk management.
 For details of Appendix QR B, please refer to Appendix E and JCB Regulatory Publications for QR
Code Payment – Operations Manual.

5.5.3. Implementation Stage

At the implementation stage, the Acquirer shall complete:

 Development and debugging of its authorization host system and settlement

system (if necessary).
 Development and validation of the merchant application (or website for
merchant) against the Acquirer’s mobile application (or website) service level
and security requirements.
 Note: Those Acquirers who do not yet support single message processing shall
develop their settlement host system to be capable of clearing and settlement without generating
Outgoing Interchange File from JCBI.

 For details of authorization system requirements, please refer to JCB Regulatory Publications –
System Specifications – Online Interface Guide for QR Code Payment.

 For details of settlement system requirements, please refer to JCB Regulatory Publications – System
Specifications – Batch Interface Guide for QR Code Payment.

5.5.4. Testing Stage

At the testing stage, the Acquirer shall complete a QR Code Generation Test, Sandbox
Test (self-test in the Sandbox Test environment), API Test for QR Code Payment, and
File Import Test for batch files.

The API Test and File Import Test are interactive tests between the Acquirer and JCBI.
The Acquirer shall request its JCBI representative to arrange the test schedule.

5.5.4.1. QR Code Generation Test (for MPM)

The purpose of this test is to ensure that Acquirer’s QR Code generation system (for
example, the Acquirer’s internal system, webpage for merchants, and merchant
application) properly generates QR Codes in accordance with EMVCo specifications.
This is a self-test by the Acquirer.

May/2018 © 2018 JCB International All Rights Reserved Page 38

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
5. Acquirer Requirements

 The Acquirer shall perform the self-test for Static and Dynamic QR Code
generation in accordance with Appendix F.

 Acquirer shall submit the Test Report (Appendix G) to JCBI for confirmation.

5.5.4.2. Sandbox Test for QR Code Payment

The purpose of this test is to validate that the API messages are correctly generated by
the Acquirer’s authorization host in accordance with the JCB Regulatory Publications -
System Specifications – Online Interface Guide for QR Code Payment. This test is a
self-test performed by the Acquirer in the Authorization System for QR test
environment. This test may be used for debugging purposes as well.

The successful completion of the Sandbox Test is the criteria to proceed to API Test in
the interaction environment.

 JCBI provides the technical implementation details, which includes the details of
the test cases to be executed and the procedure for executing the self-test.
 JCBI prepares client and server security test certificates and distributes them to
the Acquirer.
 JCBI configures the IP address white listing in the Sandbox Test environment
allowing the Acquirer to perform the Sandbox Test.
 The Acquirer shall make secured connection to the Sandbox Test environment
and execute the test cases as Acquirer.
 The Acquirer shall use the Sandbox Test environment to simulate the Issuer and
Cardmember.
 The Acquirer shall submit the test results captured during the self-test to JCBI
for validation.

A batch interface test (including exchange of settlement summary data, reconciliation

data, and other batch files) is out of scope of the Sandbox Test. The same process as for
traditional card payments shall apply. If the Acquirer supports new functions, changes
the file transfer method, or changes any other operational procedure when implementing
JCB QR Code Payment, JCBI may request the Acquirer to perform additional tests
which are not specified in this document.

May/2018 © 2018 JCB International All Rights Reserved Page 39

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
5. Acquirer Requirements

5.5.4.3. API Test for QR Code Payment

The purpose of this test is to validate that the API messages are correctly generated by
the Acquirer’s authorization host in accordance with the JCB Regulatory Publications -
System Specifications – Online Interface Guide for QR Code Payment.

As this test is an interactive test with JCBI, the Acquirer shall request its JCBI
representative to arrange the test schedule.

The successful completion of the API Test is the criteria to proceed to the Migration
Test.

 Upon the successful completion of the Sandbox Test, JCBI provides the
schedule for the API Test.
 Acquirer shall connect to the Authorization System for QR test environment and
execute the online test cases with JCBI.

If the Acquirer supports new functions, changes the file transfer method, or changes any
other operational procedure when implementing JCB QR Code Payment, JCBI may
request the Acquirer to perform additional tests which are not specified in this
document.

5.5.4.4. File Import Test for QR Code Payment

The purpose of this test is to validate that the Acquirer host system is capable of
receiving batch files provided by JCBI, such as settlement summary data and
reconciliation data, which includes the Licensee ID and newly assigned AIN.

 The Acquirer shall execute the batch test cases with JCBI to ensure that its host
system is capable of receiving the batch files (for example, settlement data and
reconciliation data).

5.5.4.5. Migration Test and Service Launch

The purpose of this test is to ensure that the Acquirer is ready to go live and release JCB
QR Code Payment to Merchants.

May/2018 © 2018 JCB International All Rights Reserved Page 40

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
5. Acquirer Requirements

The Migration Test shall be completed when both parties confirm all the test
transactions specified by JCBI are successful in the production environment, which
includes online API connectivity as well as the batch file exchange and data import.

 Upon successful completion of the API Test, Acquirer shall agree with JCBI on
the Migration Plan and other preparation requirements to be made before the
first transaction.
 Acquirer shall receive a Live Operation Reference (LOR) from JCBI as the
service guide for system related operations (including system maintenance
procedures and emergency procedures).

5.5.5. Post Launch Stage

5.5.5.1. Monthly Report from Acquirer

The Acquirer shall submit a Monthly Report for JCB QR Code Payment to JCBI within
the first 10 business days of every month. The Monthly Report format is provided in
Appendix C .

May/2018 © 2018 JCB International All Rights Reserved Page 41

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix A: Transaction Flows

Appendix A: Transaction Flows for Standard and Exceptional

Processes

A-1 Introduction

A-2 Normal Transaction Flows

A-2.1 Purchase Transaction Flow
A-2.2 Reversal Transaction Flow
A-2.3 Time Out Reversal Transaction Flow
A-2.4 Reject Advise Transaction Flow
A-2.5 Transaction Status Inquiry Flow

A-3 Additional Service Transaction

A-3.1 Exchange Rate Lookup Flow

May/2018 © 2018 JCB International All Rights Reserved Page 42

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix A: Transaction Flows

A-1. Introduction
This Appendix A gives several examples of the normal MPM transaction flows and
additional service transaction flow.

A-2. Normal Transaction Flows

This section describes some different transaction flows. The transaction flows are
described from the perspective of the participants involved in the message flow:
1. Issuer
2. JCBI
3. Acquirer

A-2-1 Purchase Transaction Flow

The Purchase Transaction has 5 participants. The transaction is initiated by the Issuer.
1. The Cardmember requests a purchase transaction by scanning the QR Code
using the mobile application and confirming the transaction with CVM as
required.

May/2018 © 2018 JCB International All Rights Reserved Page 43

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix A: Transaction Flows

2. The Issuer secures available funds in the Cardmember account or debits the
account and sends the transaction to JCBI.

3. JCBI routes the transaction to the Acquirer.

4. The Acquirer credits the Merchant account and sends a transaction response to
JCBI.

5. The Acquirer notifies the Merchant of the transaction result (either approved or
declined).

6. JCBI sends the transaction response back to the Issuer.

7. The Issuer sends Cardholder Notification to the Cardmember via the mobile
application.

A-2-2 Reversal Transaction Flow

The Reversal transaction has 5 participants. The transaction is initiated by the Acquirer.
1. The Merchant requests the Acquirer to initiate a reversal transaction, for reason
of a Cardmember dispute or on its own initiative. The request may be

May/2018 © 2018 JCB International All Rights Reserved Page 44

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix A: Transaction Flows

generated through the merchant application or the Acquirer’s back office

operation using the original transaction details from its system.
2. The Acquirer sends the reversal transaction to JCBI.
3.1 JCBI routes the transaction to the Issuer.
3.2 The Issuer credits the Cardmember account and sends a transaction response
to JCBI. If there is no response, JCBI retries the configured number of times.
3.3 The Issuer notifies the Cardmember of the transaction result (either approved
or declined).
4. JCBI sends the transaction response to the Acquirer.
5. The Acquirer notifies the Merchant of the transaction result.

A-2-3 Time Out Reversal Transaction Flow

The Timeout Reversal has 5 participants. This transaction is initiated by JCBI in when
there is no response from the Acquirer to a Purchase transaction.

May/2018 © 2018 JCB International All Rights Reserved Page 45

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix A: Transaction Flows

1. The Cardmember requests a purchase transaction by scanning the QR Code

using the mobile application and confirming the transaction with the CVM if
required.

2. The Issuer secures available funds in the Cardmember account or debits the
account and sends the transaction to JCBI.

3. JCBI routes the transaction to the Acquirer.

4. The Acquirer does not send a transaction response to JCBI within 30 seconds.
5.1 JCBI initiates the Timeout Reversal transaction to the Acquirer. If there is no
response, JCBI retries the configured number of times.
5.2 The Acquirer notifies the Merchant of the transaction result (rejected).
5.3 The Acquirer sends the transaction response to JCBI.
6. JCBI sends the transaction response (rejected) to the Issuer.
7. The Issuer notifies the Cardmember of the transaction result (rejected).

 Note: Step5.2, 5.3 and 6 may be processed at the same time or Step 6 may come first.

A-2-4 Reject Advise Transaction Flow

A Reject Advise transaction has 5 participants. The transaction is initiated by JCBI

when a Purchase transaction is rejected during JCBI general validation, and the option
of Cardmember notification is configured.
1. The Cardmember requests a purchase transaction by scanning the QR Code
using the mobile application and confirms the transaction with the required

May/2018 © 2018 JCB International All Rights Reserved Page 46

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix A: Transaction Flows

CVM if required.
2. The Issuer secures available funds in the Cardmember account or debits the
account, and sends the transaction to JCBI.
3. If JCBI general validation fails, JCBI rejects the transaction back to the Issuer.
4. JCBI sends the Reject Advise Transaction to the Acquirer.

5. The Acquirer sends the Merchant Notification to Merchants for the result of
transaction (rejected).

6. The Issuer sends the Cardmember Notification to Cardmember for the result of
transaction (rejected).

May/2018 © 2018 JCB International All Rights Reserved Page 47

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix A: Transaction Flows

A-2-5 Transaction Status Inquiry Flow

The Transaction Status Inquiry has 3 participants. This inquiry is initiated by the Issuer
or Acquirer in order to check the status of a transaction.

The request may be made in any of these ways:

(a) The Cardmember uses the mobile application or contacts the Issuer customer
support to request a transaction status inquiry.
(b) The Merchant uses the merchant application or contacts the Acquirer customer
support to request a transaction status inquiry.
(c) The Issuer or Acquirer may initiate a transaction status inquiry if a transaction is in
dispute.

May/2018 © 2018 JCB International All Rights Reserved Page 48

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix A: Transaction Flows

1. The Cardmember or Merchant sends a Transaction Status Inquiry to the Issuer

or the Acquirer.
2. The Issuer or Acquirer sends the inquiry to JCBI.
3. JCBI sends a response to the Issuer or Acquirer.
4. The Issuer or Acquirer sends the response to the Cardmember or Merchant if
they made the original request.

A-3 Additional Service Transaction

A-3-1 Exchange Rate Lookup Flow

The Exchange Rate Lookup has 2 participants. The lookup is initiated by the Issuer or
Acquirer in order to obtain an exchange rate for a crossborder transaction (the
Cardmember billing currency is different from the transaction currency).
 This function is not supported as of February 2018. JCBI may introduce this function in the future.

May/2018 © 2018 JCB International All Rights Reserved Page 49

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix A: Transaction Flows

1. The Issuer or Acquirer sends the lookup to JCBI, which contains the source
currency, source amount and target currency.
2. JCBI uses the JCBI exchange rate to convert the source amount to the target
amount and sends the response to the Issuer or Acquirer

May/2018 © 2018 JCB International All Rights Reserved Page 50

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix B: QR Code Specification for JCB Merchant

Appendix B: QR Code Specification for JCB Merchant

Table B-1 lists the name of the data object, the ID, the format of the value, the length, and
whether the presence of the data object at the root level of the QR Code is Mandatory (M),
Conditional (C), or Optional (O).

Table B-1: Data Objects under the Root of a QR Code

Name ID Format Length Presence Comment

Payload Format 00 N 02 M ‘01’

Indicator

Point of Initiation 01 N 02 O ‘11’:Static QR Code

Method
‘12’:Dynamic QR Code

Merchant Account 13 ans var. up to M The value must include the

Information 99 length of the Merchant Account
ID followed by the Merchant
Account ID (either Merchant
PAN or Partial Merchant PAN).

Ex: 13163158123456789012

14 ans var. up to - Data object reserved for future

99 use of JCB.

*The Acquirer should contact

JCBI if it needs to use ID 14.

Merchant Category 52 N 04 M
Code

Transaction 53 N 03 M
Currency

Transaction 54 ans var. up to C Absent if the mobile app

Amount 13 prompts the Cardmember to
enter the transaction amount.
Present otherwise.

May/2018 © 2018 JCB International All Rights Reserved Page 51

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix B: QR Code Specification for JCB Merchant

Name ID Format Length Presence Comment

Tip or Convenience 55 N 02 O
Indicator

Value of 56 ans var. up to C Presence of these data objects

Convenience Fee 13 depends on the presence and
Fixed value of the Tip or Convenience
Indicator.

Value of 57 ans var. up to C

Convenience Fee 05
Percentage

Country Code 58 ans 02 M

Merchant Name 59 ans var. up to M

25

Merchant City 60 ans var. up to M

15

Postal Code 61 ans var. up to O

10

Additional Data 62 S var. up to O The Additional Data Field

Field Template 99 Template includes information
that may be provided by the
Merchant or may be populated
by the mobile app to enable or
facilitate certain use cases.

For the list of data objects that

may be included in this template,
please refer to EMV QR Code
Specification.(Merchant-Present
ed Mode)

May/2018 © 2018 JCB International All Rights Reserved Page 52

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix B: QR Code Specification for JCB Merchant

Name ID Format Length Presence Comment

Merchant 64 S var. up to O The Merchant Information—

Information— 99 Language Template includes
Language Template merchant information in an
alternate language and may use
a character set different from the
Common Character Set. It
provides an alternative to the
merchant information under the
root.

For the list of data objects that

may be included in this template,
please refer to EMV QR Code
Specification.(Merchant-Present
ed Mode)

RFU for EMVCo 65-7 S var. up to O Data objects reserved for

9 99 EMVCo

Unreserved 80-9 S var. up to O Unreserved Templates

Templates 9 99

CRC 63 ans 04 M

 Please refer to EMV QR Code Specification (Merchant-Presented Mode), if other information is

needed.

May/2018 © 2018 JCB International All Rights Reserved Page 53

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix C: Monthly Report Format for QR Code Payment

Appendix C: Sample of Appendix QR A: Monthly Report Format

for QR Code Payment

The Monthly Report format for QR Code Payment shall be provided by your JCBI
representative. Please contact JCBI when needed.

JCB Regulatory Publications

Operations Manual
Appendix 1-12

JCB CARD MONTHLY REPORT for JCB QR Code Payment -MPM-

TO: FROM: Date of Report (mm/dd/yyyy):
JCB International Co., Ltd. ISS/ACQ’s Name: / /
Sales & Marketing Contact Person: SEQ:
Fax: +81-3-5778-8377 Fax:
Phone: LCID (JCB USE ONLY):
E-mail:
Card Name (Optional） : (Please select from the choices ) IIN
Report of: Card Product:
Product、Grade等を記入するこの欄を消して、
Person:
1枚で提出が済むようにする。
Month Year Card Grade:

【ISS】
(1) Balance of the Reporting Month
Cancelled Cards of the Reporting
Balance of Previous Month New Cards of the Reporting Month Balance of the Reporting Month
Product Type Month
No. of Cards No. of Accounts No. of Cards No. of Accounts No. of Cards No. of Accounts No. of Cards No. of Accounts
Credit
Debit
Prepaid
TOTAL 0 0 0 0 0 0 (a) 0 (b) 0
(2) Transaction of the Reporting Month
Number of Transactions Transaction Amount (Currency Code: )
Inter- Inter-Regional
Product Type Domestic Transaction Regional &
Domestic Transaction & Intra-
TOTAL TOTAL
On-us Local Intra- On-us Local Regional
TOTAL TOTAL
Transaction Transaction Regional Transaction Transaction Transaction
Credit 0 0 0 0
Debit 0 Cross-Border 0 0 Cross-Border 0
Prepaid 0 開始までなし 0 0 開始までなし 0
TOTAL 0 0 0 0 0 0 0 0 0 0
(3) Active Cards/Accounts in Reporting Month
No. of Cards No. of Accounts
Active Balance of Date(mm/dd/yyyy): / /
(c) (d)
the Reporting Month

Authorized
for DomesticTransaction
Signature:
for Inter-Regional & Intra-Regional Cross-Border
Transaction 開始までなし Name in Print:
Active Ratio (c)/(a) #DIV/0! (d)/(b) #DIV/0! Title:
【ACQ】
Number of merchant
Number of Transaction
Transaction Amount

May/2018 © 2018 JCB International All Rights Reserved Page 54

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix D: Sample Form QR A

Appendix D: Sample of Form A (revised for QR)

Form A revised for QR Code Payment shall be introduced later. Please contact your
JCBI representative when needed.

May/2018 © 2018 JCB International All Rights Reserved Page 55

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix E: Sample Form QR B

Appendix E: Sample of Appendix QR B: AIN Request Form

Appendix QR B shall be introduced later. Please contact your JCBI representative when
needed.

May/2018 © 2018 JCB International All Rights Reserved Page 56

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix G: Sample Test Report for QR Code Scanning and Generating

Appendix F: Self-Test for QR Code Scan and Generation

Appendix F provides the self -test cases for the Issuer QR Code Scanning Test and the
Acquirer QR Code Generation Test.

Appendix F shall be introduced later. Please contact your JCBI representative when
needed.

May/2018 © 2018 JCB International All Rights Reserved Page 57

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide
Appendix G: Sample Test Report for QR Code Scanning and Generating

Appendix G: Sample of Appendix QR C: Test Report for QR

Code Scan and Generation

Test Report for QR Code Scanning and Generating Test is described in this section. The
official Test Report format is provided by your JCBI representative

May/2018 © 2018 JCB International All Rights Reserved Page 58

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.
 JCB QR Code Payment Implementation Guide

JCB QR Code Payment Implementation Guide

Ver. 1.0

Date of Issue: May 2018

Issued by: JCB International Co. Ltd.

© 2018 JCB International Co., Ltd.

Unauthorized reproduction is strictly prohibited.

May/2018 © 2018 JCB International All Rights Reserved Page 59

NOTE: This information, provided by JCBI, is confidential and proprietary and may not be duplicated, published or disclosed
to any third party, in whole or in part, without the express written permission of JCBI.