0% found this document useful (0 votes)

1K views

JCB Online Interface Guide (2019)

Uploaded by

mitxael83

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

1K views

JCB Online Interface Guide (2019)

Uploaded by

mitxael83

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 87

Main Index

JCB Regulatory Publications

System Specifications – Online Interface Guide
Table of Contents

Table of Contents
1 INTRODUCTION .................................................................................... 4

1.1 PURPOSE OF THIS DOCUMENT ....................................................................................................4

1.2 INTENDED READERS ...................................................................................................................4
1.3 RELATED DOCUMENTS ...............................................................................................................5
1.4 CODE ASSIGNMENT.....................................................................................................................5

2 SUMMARY OF J-LINK SPECIFICATIONS ........................................ 6

2.1 J-LINK OVERVIEW ......................................................................................................................6

2.2 SUPPORTED CARD APPLICATIONS...............................................................................................6
2.3 COMMUNICATION PROTOCOL REQUIREMENTS ...........................................................................7
2.3.1 TCP/IP ........................................................................................................................7
2.4 GENERAL FORMAT FOR ONLINE MESSAGES ...............................................................................8
2.4.1 Message Type ..............................................................................................................8
2.4.1 Bit Maps......................................................................................................................8
2.4.2 Data Elements..............................................................................................................8
2.5 MESSAGE, TRANSACTION, APPLICATION ....................................................................................9
2.5.1 Message ......................................................................................................................9
2.5.2 Transaction ..................................................................................................................9
2.5.3 Application ..................................................................................................................9
2.6 MESSAGE IDENTIFICATION .......................................................................................................10
2.7 MAGNETIC STRIPE DATA ..........................................................................................................10
2.8 TIMER VALUES .........................................................................................................................10
2.8.1 Authorization request message time-out interval (t100)............................................... 10
2.8.2 Authorization advice message time-out interval (t120)................................................ 10
2.8.3 Record registration/inquiry request message (t302)..................................................... 10
2.8.4 Reversal time-out interval (t420) ................................................................................ 10
2.8.5 Echo interval (t800) ................................................................................................... 11
2.8.6 Time-out interval for Sign-on or Sign-off message (t800) ........................................... 11
2.8.7 Time-out for Dynamic Key Exchange message (t800) ................................................ 11

3 ONLINE TRANSACTIONS .................................................................. 12

3.1 TRANSACTION STATE ...............................................................................................................12

04/01/2019 © 2019 JCB International All Rights Reserved Page 1

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

JCB Regulatory Publications

System Specifications – Online Interface Guide
Table of Contents

3.1.1 Initial State ................................................................................................................ 12

3.1.2 Final State ................................................................................................................. 13
3.2 AUTHORIZATION REQUEST TRANSACTION ...............................................................................13
3.2.1 Message types............................................................................................................ 13
3.2.2 Transition of the transaction state ............................................................................... 13
3.2.3 Authorization request related service .......................................................................... 15
3.3 AUTHORIZATION ADVICE TRANSACTION .................................................................................16
3.3.1 Message types............................................................................................................ 16
3.3.2 Transition of the transaction state ............................................................................... 16
3.4 RECORD REGISTRATION/INQUIRY REQUEST TRANSACTION .....................................................18
3.4.1 Message types............................................................................................................ 18
3.1.1 Transition of the transaction state ............................................................................... 18
3.5 REVERSAL ADVICE TRANSACTION ...........................................................................................20
3.5.1 Message types............................................................................................................ 20
3.5.2 Transition of the transaction state ............................................................................... 20
3.5.3 Reversal related service.............................................................................................. 22
3.6 NETWORK MANAGEMENT TRANSACTION.................................................................................22
3.6.1 Message types............................................................................................................ 23
3.6.2 Transition of the transaction state ............................................................................... 23
3.6.3 Network management functions ................................................................................. 24
3.6.4 0801 Network management request repeat message .................................................... 25
3.7 ADMINISTRATIVE TRANSACTION ..............................................................................................25
3.7.1 Message types............................................................................................................ 26
3.7.2 Transition of the transaction state ............................................................................... 26

4 ONLINE APPLICATIONS ................................................................... 27

4.1 AUTHORIZATION APPLICATION ................................................................................................27

4.2 RECORD REGISTRATION/INQUIRY APPLICATION ......................................................................28
4.3 SUMMARY OF APPLICATION FEATURES ....................................................................................29

5 MESSAGE FORMAT ............................................................................ 30

5.1 BIT MAP ALLOCATION LISTS ....................................................................................................30

5.1.1 Abbreviations used in figures ..................................................................................... 30
5.1.2 Authorization Message Class ..................................................................................... 31
5.1.3 Record Registration/Inquiry Message Class ................................................................ 37
5.1.4 Reversal Message Class ............................................................................................. 38
5.1.5 Administrative Message Class.................................................................................... 42

04/01/2019 © 2019 JCB International All Rights Reserved Page 2

JCB Regulatory Publications

System Specifications – Online Interface Guide
Table of Contents

5.1.6 Network Management Message Class ........................................................................ 43

5.2 DATA ELEMENTS OF J-LINK9 ....................................................................................................43

APPENDIX OIG-1 RESPONSE CODE MAPPING .................................... 88

APPENDIX OIG-2 SAMPLE TRANSACTION FLOW ............................. 92

APPENDIX OIG-3 MESSAGE SAMPLES ................................................ 102

APPENDIX OIG-4 BIT 120 FORMAT EXAMPLES ................................ 134

APPENDIX OIG-5 CODE LIST FOR ONLINE INTERFACE GUIDE .. 151

APPENDIX OIG-6
ONLINE AUTHORIZATION REQUEST MESSAGE (#0100)
DATA REQUIREMENT ..................................................................... 152

04/01/2019 © 2019 JCB International All Rights Reserved Page 3

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 1 Introduction

1 Introduction
1.1 Purpose of This Document
“Online Interface Guide” is primarily intended to describe J-Link, which is the ISO
8583:1987-based specification of the rules and formats for online message
interchange with the JCBI Network.
This document includes information on online transaction states, online application
types, message formats, and communication protocols supported by J-Link. This
document mainly focuses on the interface between the Licensee’s system and
J/Bridge.
ATTENTION: Do NOT start programming with only this document.

 NOTE: The specifications described in this document are only general definitions. Before the
start of programming or implementation of J-Link in the Licensee’s system, the details of the
specifications should be discussed and agreed upon by the Licensee and JCBI.

1.2 Intended Readers

This document is intended for all personnel responsible for planning and/or
implementing the Licensee-JCBI system project, including:
• Project leaders
• System development supervisors
• Application programmers who will implement the J-Link
specifications for the Licensee’s system
• System administrators
• Test support supervisors
• System operation supervisors

04/01/2019 © 2019 JCB International All Rights Reserved Page 4

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 1 Introduction

Readers are expected to have an understanding of the following:

• Basic card applications
• ISO 8583:1987
• TCP/IP (if involved in the technical aspect of implementation)

1.3 Related Documents

These documents will be prepared by JCBI before the start of programming or
implementation of J-Link in the Licensee’s system.
• Project Plan
This document provides the overall plan for the system implementation project. It
contains such information as project overview, system and processing flow, system
configuration, requirements, formation, relevant documents, and the master
schedule.
• JCB Licensee Testing Guide
This document establishes the guidelines for Function Test, EDI Transmission Test,
and Certification Test required for Licensees who wish to begin acquiring or issuing
business for JCBI or implement new functions into the host system, and for use of
the JCB Test Simulator.

1.4 Code Assignment

Licensees are required to set unique values assigned by JCBI in J-Link. JCBI
assigns such Licensee-unique codes and informs the Licensee with
Appendix-OIG-5 at least 1 month before the Licensee commences operations or
when any change are required to these values.

04/01/2019 © 2019 JCB International All Rights Reserved Page 5

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 2 Summary of J-Link Specifications

2 Summary of J-Link Specifications

2.1 J-Link Overview
The purpose of J-Link is to define the interface between the Licensee’s system and
J/Bridge on both the application level and the communication level.
J-Link specifies the communication protocol and application protocol between the
two systems.

Figure 2-1 J-Link Interface

Licensee J/Bridge Licensee

System System

J-Link J-Link

2.2 Supported Card Applications

J-Link supports major online card applications which can be implemented according
to the definitions of ISO 8583:1987. The applications currently supported are as
follows:
• POS/ATM online authorization message exchange
• Record registration/inquiry
The formal definitions of this term and the terms ‘transaction’ and ‘message’ are
described under ‘Message, Transaction, Application’ in this chapter.

04/01/2019 © 2019 JCB International All Rights Reserved Page 6

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 2 Summary of J-Link Specifications

2.3 Communication Protocol Requirements

TCP/IP is used as the inter-system communication protocols between the Licensee’s
system and J/Bridge.

2.3.1 TCP/IP
J/Bridge supports TCP/IP (Transfer Control Protocol/Internet Protocol) interface.
2.3.1.1 Physical Layer & Data Link Layer
IEEE802.3 and IEEE802.2
10Base-T or 100BASE-TX (uses Unshielded Twisted-Pair Cable)
2.3.1.2 Network Layer & Transport Layer
The parameters for TCP/IP are defined as follows:
IP Address JCBI shall assign the specified IP address for licensee.
Do not change the JCB assigned IP address.
Subnet 255.255.255.0
TCP Port Numbers JCBI shall assign the specified number for licensee.
Server or Client Licensee’s system: Server, J/Bridge: Client

2.3.1.3 Message Format

Messages transmitted between the licensee host and J/Bridge require a 4-byte length
indicator followed by the application data. This 4-byte length field identifies the
length of the data that follows.

IP Header TCP Header Data Header Data (Length number of bytes)

(4bytes)
Length of Data Application Data

TCP data

First 2-bytes of the Data Header is used for identifying the length of the data.
X’0000’ must be set in last 2-bytes.
Message Format Example
If the data length is 500 bytes, the message would be as follows:
Data Data (Length number of bytes)
Header
X’01F40000’ 500 bytes of data

04/01/2019 © 2019 JCB International All Rights Reserved Page 7

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 2 Summary of J-Link Specifications

2.4 General Format for Online Messages

The J-Link application message format is based on ISO 8583:1987. No message
headers are supported in J-Link. The data elements of messages are described in
detail in Chapter 5.

Figure 2-3 General format for application messages (including network control)

Message Type Bit Maps Data Elements

2.4.1 Message Type

The message type is a 4-digit numeric field. J-Link supports the following message
types:
• 01xx Authorization messages
• 03xx Record registration/inquiry messages
• 04xx Reversal messages
• 06xx Administrative messages
• 08xx Network management messages

2.4.1 Bit Maps

The second message component is one or two bit maps, each consisting of 64 bits
numbered from the left, starting with bit ‘1’. Each bit signifies the presence (1) or
the absence (0) in the message of the data element associated with that particular bit.
The first bit within the primary bit map (bits 1-64), when valued as ‘1’, denotes the
presence of the secondary bit map (bits 65-128).
The primary bit map always exists and the most frequently used data elements are
indexed from the primary bit map.

2.4.2 Data Elements

The third message component is a series of data elements. The data elements in a
message are indexed in the bit maps. Some data elements are of fixed length and
the others are variable length. The details of each data element are described in
Section 5.2.

04/01/2019 © 2019 JCB International All Rights Reserved Page 8

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 2 Summary of J-Link Specifications

2.5 Message, Transaction, Application

J-Link categorizes card-originated transaction messages and their application
processing as follows:

2.5.1 Message
A message is the elemental unit of a transaction and is used to convey information
between systems. It consists of a message type identifier, bit maps and a set of data
elements as defined in the previous section. Transmission headers and other
attachments are not considered part of the message.

2.5.2 Transaction
A transaction is a message set made up of a request or advice message and the
subsequent corresponding messages, such as repeat or response messages.

2.5.3 Application
An application represents a specific type of message processing, and consists of a set
of transactions.
For example, the authorization application consists of an authorization request
transaction, a reversal advice transaction, and an optional authorization advice
transaction. The authorization request transaction consists of an authorization
request message (0100) and an authorization request response message (0110).
The relationship of these is illustrated in Figure 2-4.

Figure 2-4 Authorization application, transactions, and messages

Authorization Application
Authorization Request Reversal Advice Authorization Advice
Transaction Transaction Transaction

0100 request 0420 advice 0120 advice

0110 request response 0421 advice repeat 0121 advice repeat
0430 advice response 0130 advice response

04/01/2019 © 2019 JCB International All Rights Reserved Page 9

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 2 Summary of J-Link Specifications

2.6 Message Identification

Each transaction message must be uniquely identified by the message initiator with
the following four data elements:
(a) Message type identifier
(b) Transmission date and time (bit 7)
(c) System trace audit number (bit 11)
(d) Acquirer institution identification code (bit 32)

2.7 Magnetic Stripe Data

The magnetic stripe data must be carried in the message-as-received format from the
POS/ATM devices. Note that Track 3 data is not recognized by J-Link. If such
data exists in a message, it is ignored and dropped from the message when
forwarded.
 NOTE: The track data encoded on a magnetic stripe may not be included in the Authorization
Request message on rare occasions, even if the magnetic stripe is swiped in a valid
Transaction. Issuers should acknowledge that for Transactions that apply to the above, the
value “X’00’ Unknown” is set in “Bit 22 Point of service entry mode” of the Authorization
Request message.

2.8 Timer Values

2.8.1 Authorization request message time-out interval (t100)
Recommended value is 30 seconds for Acquirers, 15 seconds for Issuers. The actual
value may differ depending on network configuration.

2.8.2 Authorization advice message time-out interval (t120)

Recommended value is 20 seconds for Acquirer, 15 seconds for Issuers. The actual
value may differ depending on network configuration.

2.8.3 Record registration/inquiry request message (t302)

Recommended value is 30 seconds for Issuers. The actual value may differ
depending on network configuration.

2.8.4 Reversal time-out interval (t420)

Recommended value is 30 seconds for Acquirer, 15 seconds for Issuers. The actual
value may differ depending on network configuration.

04/01/2019 © 2019 JCB International All Rights Reserved Page 10

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 2 Summary of J-Link Specifications

2.8.5 Echo interval (t800)

Recommended value is 180 seconds. Actual value may differ depending on
estimated amount of message traffic.

2.8.6 Time-out interval for Sign-on or Sign-off message (t800)

Recommended value is 90 seconds.

2.8.7 Time-out for Dynamic Key Exchange message (t800)

Time-out interval is set to at least 30 seconds.
In addition to the timer value, the maximum number of retries is twice.
If the KEP exchange fails three times, JCBI and the Licensee will cooperate to
resolve the problems.

04/01/2019 © 2019 JCB International All Rights Reserved Page 11

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

3 Online Transactions
This chapter specifies the requirements for online transaction processing, particularly
in terms of the transaction state.
The message types (as defined in ISO 8583:1987) listed below are used for online
transactions. Usage of the message types does not deviate from the ISO definitions,
and messages other than those listed here are not allowed by J-Link and are thus
treated as unrecognized messages.
Figure 3-1 Message Types
Message Transaction Class
0100, 0110 authorization request
0120, 0121, 0130 authorization advice
0302, 0312 record registration/inquiry
0420, 0421, 0430 reversal advice
0620, 0630 administrative
0800, 0810 network management

 NOTE: The message types which are used for a particular connection depend on
the Licensee’s situation.

3.1 Transaction State

Because card processing transactions may occur in large volumes and may require
quick responses at any time, unnecessary advice repeats should be eliminated so as
to avoid degrading system availability. In most cases, such unnecessary advice
repeats are due to an insufficiency of specifications for identifying whether the
transaction has been finished.
In J-Link, needless advice traffic is minimized and continuous online applications are
maintained by defining two basic states, initial and final, for all transactions. By
identifying the current state of a transaction, the system that initiated a message can
quickly determine what should be done next for the transaction.

3.1.1 Initial State

Initiation of a transaction is normally the role of an Acquirer system, though Issuer
systems may also initiate advice messages and record registration/inquiry messages.
The initial state indicates that the transaction is in progress, and this state continues
until the next event (state change) occurs for the transaction.

04/01/2019 © 2019 JCB International All Rights Reserved Page 12

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

3.1.2 Final State

Completion of the transaction is the role of the Issuer system, though JCBI system
may also complete record registration/inquiry messages.
The final state indicates whether or not the transaction was completed successfully.
The Acquirer system (or message-initiating system) identifies the final state by
either receiving the response or detecting a time-out.
Figure 3-2 in this chapter shows the states and transition stages for each type of
online transaction are defined.

3.2 Authorization Request Transaction

The authorization transaction provides approval or guarantee of funds from the Issuer
to the Acquirer. It is not intended to permit the application of the approved
transaction amount to the cardholder's account, so no reconciliation is required.

3.2.1 Message types

The authorization request transaction consists of the following message types:
(a) Authorization request message (0100)
(b) Authorization request response message (0110)
All aborted transactions (request messages which do not receive the
corresponding response message within the time-out period) must be
reversed with the reversal advice message (0420), and then initiated
again as another authorization request or an advice transaction if
required.

3.2.2 Transition of the transaction state

The authorization request transaction passes from the initial state to the final state via
the stages of request, response, and exceptional condition. These stages take the
forms listed below.
(a) Initiated
The authorization transaction is initiated by the Acquirer’s sending of
an authorization request message (0100).
(b) Approved
Successful authorization must be indicated with the response code
‘00’ in the response message (0110).
(c) Declined
Unsuccessful authorization must be indicated by a negative response
code representing the denial reason as defined in ISO 8583.

04/01/2019 © 2019 JCB International All Rights Reserved Page 13

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

(d) Referral (refer to Issuer)

The response codes that are indicated as Referral in Appendix OIG-1
are used when Merchant is requested to refer the transaction to the
Issuer. This is not applicable when Merchant is not present (e.g.,
ATM devices). In such cases, the transaction is declined.
(e) Aborted (time-out)
Failure to receive a response message within the time-out period will
cause the requested authorization transaction to be aborted.
ATTENTION: The Acquirer should immediately initiate a reversal advice
message (0420) for the aborted authorization request message in order to avoid an
unnecessary reduction in the authorization limit for the cardholder’s account.

Figure 3-2 illustrates the state transition and message traffic for authorization request
transactions.

04/01/2019 © 2019 JCB International All Rights Reserved Page 14

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

Figure 3-2 State transition of authorization request transaction

1st Event Initial State 2nd Event Final State

Issuer

0110 (RC=00) Approved

Acquirer

Issuer

Acquirer
0110 (RC=43) Declined

0100 Initiated Acquirer

Issuer
Issuer

0110 (RC=01) Referral

Acquirer

t100 timeout
(no response) Aborted

3.2.3 Authorization request related service

3.2.3.1 Partial Approval
Partial approval is a service that allows Issuers to approve a portion of the requested
transaction amount. To provide the partial approval amount to Acquirers, Issuers
respond with the approved amount and a partial approval response code in the
response message.
 Refer to Appendix OIG-6 for data requirements for authorization messages.
 NOTE: Partial approval can be used if the Issuer and the Acquirer support J-Link9 and the
merchant terminal supports receipt of partial approvals.

04/01/2019 © 2019 JCB International All Rights Reserved Page 15

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

3.2.3.2 Balance Inquiry

Balance inquiry service enables Cardmembers to inquire on their account balance at
an ATM or POS terminal.
 NOTE: Balance inquiry is available only when both the Issuer and the Acquirer support
J-Link9.

3.3 Authorization Advice Transaction

The authorization advice transaction is a notification of approval or guarantee of
funds on behalf of Issuer.

3.3.1 Message types

The authorization advice transaction consists of the following message types:
(a) Authorization advice message (0120)
(b) Authorization advice repeat message (0121)
(c) Authorization advice response message (0130)

3.3.2 Transition of the transaction state

The authorization advice transaction passes from the initial state to the final state via
the stages of advice, response, and exceptional condition. These stages take the
forms listed below.
(a) Initiated
The authorization advice transaction is initiated by the Acquirer’s
sending of an authorization advice message (0120).
(b) Notified
Successful authorization must be indicated with the response code
‘00’ in the authorization advice response message (0130).
Because the advice message is notification that the authorization has
already been completed, negative response codes from the Issuer in
the advice response message (such as in the case of a cardholder who
has been recently registered in Negative File that hasn’t yet been
distributed) signify only information.
The operation managers for the Acquirer’s and the Issuer’s systems
should be warned of the occurrence of such negative advice responses.
The Acquirer cannot initiate an advice repeat message for a negative
advice response.

04/01/2019 © 2019 JCB International All Rights Reserved Page 16

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

(c) Aborted
If the time-out period expires before the corresponding response
message is received, the Acquirer system must initiate advice repeat
messages for the aborted advice message until the response message is
received or until the maximum retry count is reached.
If the response message is still not received after transmission of the
advice repeat messages, the authorization advice transaction will be
aborted.
This condition is considered a ‘suspicious system error condition’ and
the system administrator is to investigate the source of the problem.
Figure 3-3 illustrates the state transition and message traffic for authorization advice
messages.

Figure 3-3 State transition of authorization advice transaction

1st Event Initial State 2nd Event Final State

Issuer

0130 Notified

Acquirer
Acquirer

0120 Initiated

t120 timeout,
Issuer Maximum retry
count for 0121 Aborted
exceeded
(no response)

04/01/2019 © 2019 JCB International All Rights Reserved Page 17

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

3.4 Record Registration/Inquiry Request

Transaction
JCBI provides the online service of registration and inquiry of Negative File records
(negative records) in addition to the existing service through batch file transmission
and through JCB Authorization Terminal.

3.4.1 Message types

The record registration/inquiry request transaction consists of the following message
types:
(a) Record registration/inquiry request message (0302)
(b) Record registration/inquiry request response message (0312)
An Issuer may not submit Negative File record registration/inquiry requests online
continuously, unless the Licensee first implements a message flow control
mechanism for limiting the number of requests sent per second or for limiting the
number of requests sent without receiving replies.

3.1.1 Transition of the transaction state

The record registration/inquiry request transaction passes from the initial state to the
final state via the stages of request, response, and exceptional condition. These
stages take the forms listed below.
(a) Initiated
The record registration/inquiry request transaction is initiated by the
Issuer’s sending of a record registration/inquiry request message
(0302).
(b) Approved
Successful request must be indicated with the response code ‘00’ in
the response message (0312).
(c) Declined
Unsuccessful request must be indicated by a negative response code
representing the denial reason as defined in Appendix OIG-1.
(d) Aborted (time-out)
Failure to receive a response message within the time-out period will
cause the requested record registration/inquiry transaction to be
aborted.

04/01/2019 © 2019 JCB International All Rights Reserved Page 18

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

 NOTE: Whenever a record registration/inquiry request transaction is aborted, it is

recommended that an inquiry message be sent to confirm whether or not the request was
approved.
Figure 3-4 illustrates the state transition and message traffic for record
registration/inquiry request transactions.

Figure 3-4 State transition of record registration/inquiry request transaction

1st Event Initial State 2nd Event Final State

JCBI

0312 (RC=00) Approved

Issuer

Issuer
JCBI

0 302 Initiated Declined

312 (RC=29)

JCBI Issuer

t302 timeout
(no response) Aborted

04/01/2019 © 2019 JCB International All Rights Reserved Page 19

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

3.5 Reversal Advice Transaction

The reversal advice transaction is used to cancel or change the impact of a previous
authorization transaction. It is initiated when the Acquirer system detects one of
the following exceptional conditions:
(a) ATM equipment failure
(b) Partial dispensation of funds by ATM
(c) Customer cancellation
(d) Time-out (response received too late)
When the Issuer system cannot actually reverse the transaction, the negative response
code may be returned for the advice. In this case, the Acquirer and the Issuer must
investigate their transactions by exchanging transaction log files, and then enter the
results into the reconciliation files.
The Acquirer system can send reversal request repeat messages only when the
matching response message (which has the same system trace audit number or
retrieval reference number, transaction date, and time) was not received within the
time-out period.

3.5.1 Message types

The reversal advice transaction consists of the following message types:
(a) Reversal advice message (0420)
(b) Reversal advice repeat message (0421)
(c) Reversal advice response message (0430)
Issuer reversal advice messages are not supported.

3.5.2 Transition of the transaction state

The reversal advice transaction passes from the initial state to the final state via the
stages of advice, response, and exceptional condition. These stages take the forms
listed below.
(a) Initiated
The reversal advice transaction is initiated by the Acquirer’s sending
of a reversal advice message (0420). An Acquirer can send the
reversal advice message within 30 days after the original transaction
date. After passing 30 days, the Acquirer shall set a reversal
transaction in an Interchange File without sending the reversal advice
message(0420).

04/01/2019 © 2019 JCB International All Rights Reserved Page 20

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

Also an Issuer shall be able to process this message until 30 days after
an original transaction date.
(b) Notified
Successful reversal must be indicated with the response code ‘00’ in
the reversal advice response message (0430).
Because the advice message is notification that the reversal has
already been completed, negative response codes from the Issuer in
the advice response message (such as in the case of a cardholder who
has been recently registered in Negative File that hasn’t yet been
distributed) signify only information.
The operation managers for the Acquirer’s and the Issuer’s systems
should be warned of the occurrence of such negative advice responses.
The Acquirer cannot initiate an advice repeat message for the negative
advice response.
(c) Aborted
If the time-out period expires before the corresponding response
message is received, the Acquirer system must initiate advice repeat
messages for the aborted advice message up to the bilaterally agreed
maximum retry count, until the response message is received.
If the response message is still not received after transmission of the
advice repeat messages, the authorization advice transaction will be
aborted.
This condition is considered a ‘suspicious system error condition’ and
the system administrator is to investigate the source of the problem.
Figure 3-5 illustrates the state transition and message traffic for reversal advice
transactions.

04/01/2019 © 2019 JCB International All Rights Reserved Page 21

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

Figure 3-5 State transition of reversal advice transaction

1st Event Initial State 2nd Event Final State

Issuer

0430 Notified

Acquirer
Acquirer

0420 Initiated

Issuer t420 timeout,

maximum retry
count for 0421 Aborted
exceeded
(No response)

3.5.3 Reversal related service

3.5.3.1 Partial reversal transaction
The partial reversal advice is identified when the reversal advice message contains a
non-zero value in the replacement amount field (bit 95). The full reversal requires
all zeros in the replacement amount field. The partial reversal advice requires the
following:
(a) The original transaction amount in the transaction amount field (bit 4).
(b) The response code field (bit 39) should be ‘96’ (system malfunction)
or any other applicable reason code for the acquiring device's failure.
(c) Set the new (actual) transaction amount in the replacement amount
field. Trailing zeros are required as fillers, and the amount must be
in EBCDIC characters.
As with other reversal advice transactions, any erroneous conditions in the Issuer
system will result in a negative advice response.

3.6 Network Management Transaction

The network management transaction coordinates the various system operations
specified in the network management information code (bit 70).

04/01/2019 © 2019 JCB International All Rights Reserved Page 22

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

3.6.1 Message types

The network management transaction consists of the following message types:
(a) Request message (0800)
(b) Response message (0810)

3.6.2 Transition of the transaction state

The network management transaction passes from the initial state to the final state
via the stages of advice, response, and exceptional condition. These stages take the
forms listed below.
(a) Initiated
The network management transaction can be initiated by the Acquirer
or the Issuer by sending the network management request message
(0800).
Approved
Successful processing must be indicated with the response code ‘00’
in the response message (message type 0810).
(b) Declined
Unsuccessful processing must be indicated by negative response code
representing the denial reason as defined in ISO 8583.
Figure 3-6 illustrates the state transition and message traffic for network
management transactions.

04/01/2019 © 2019 JCB International All Rights Reserved Page 23

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

Figure 3-6 State transition of network management transaction

1st Event Initial State 2nd Event Final State

Rece iver

0810 (RC=00) Approved

Orig inator
Originator

0800 Initiated

Rece iver
Receiver

0810 (RC=91) Declined

Originator

t800 t imeout
(no response) Aborted

3.6.3 Network management functions

J-Link requires the following network management functions, which are specified in
5.2 / 5.3 Data Elements (Bit 70)
3.6.3.1 Sign-on
The sign-on function is for activating system linkage and applications. By
receiving a positive response message, the system that initiated the transaction can
recognize that the other Licensee’s system is ready. If a negative response is
returned, the other Licensee’s system is considered inactive.

04/01/2019 © 2019 JCB International All Rights Reserved Page 24

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

3.6.3.2 Sign-off
The sign-off function is for deactivating system linkage and applications. Even if a
negative response is returned, or no response is returned, the system that initiated the
transaction can stop its activities. However, no response or a negative response
indicates exceptional system status, so the system operator should investigate the
cause of the trouble.
3.6.3.3 Echo test
The echo test transaction is for checking whether or not the linkage is active. By
receiving a response message, the initiating system can recognize that the Licensee’s
system link is active.

3.6.3.4 Dynamic Key Exchange

Dynamic Key Exchange service enables Licensees to change their KPE value
through online messages. The originator (the Licensee system or J/Bridge) sends a
request to change KPE value using 0800 message. If the receiver system (the
Licensee system or J/Bridge) successfully changes the KPE value it will return a
0810 response message with the value of 00 in Bit39 (Response Code) to the
originator. If the key exchange fails, the 0810 response message will have a value
other than 00 in Bit 39 (Response Code).
 Refer to Appendix OIG-2.2.3 for the details of transaction flows.

3.6.4 0801 Network management request repeat message

Current J-Link specifications does not allow 0801 network management request
repeat message.

3.7 Administrative Transaction

J-Link supports the 0600 series of messages for sending administrative information
to the Licensee’s system. The administrative transaction is used to provide
notification of an unrecognized message. If a message cannot be recognized by the
receiver, the originator must be notified with the 0620 message with the received
message text attached.
The copies of unrecognized messages should be carried in bit 48 (additional data -
private).
Figure 3-7 shows the transaction flow when an unrecognized message is received.

04/01/2019 © 2019 JCB International All Rights Reserved Page 25

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 3 Online Transactions

Figure 3-7 Notification of an unrecognized message

Licensee Licensee
????
unrecognized
message

0620

0630

3.7.1 Message types

The administrative transaction consists of the following message types:
(a) Administrative advice message (0620)
(b) Administrative response message (0630)
Since this type of transaction is for sending administrative information only, no
response is required.
However, message identification must be established (i.e., it must be unique with
reference to all other transactions initiated) with the system trace audit number and
the transaction date and time. The purpose of the 0620 message is to notify the
transaction initiator of the occurrence of an invalid message. The originator of the
0620 message does not need the 0630 response message, so the 0630 message is
optional in J-Link.

3.7.2 Transition of the transaction state

The administrative advice transaction has only one state, and thus no transition takes
place.
(a) Sent
The administrative transaction is only for sending miscellaneous
information to the Licensee’s system, so no special processing is
required of the receiving system.

04/01/2019 © 2019 JCB International All Rights Reserved Page 26

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 4 Online Applications

4 Online Applications
The following two types of online applications are currently supported by J-Link:
(a) Authorization application
(b) Record registration/inquiry application
The Licensee system does not need to have complete implementation for all
applications. Only the transactions for applications performed with the individual
Licensee are required (refer to Section 4.3, ‘Summary of Application Features‘).

4.1 Authorization Application

The authorization application consists of the following transactions:
(a) Authorization request (0100-0110)
(b) Authorization advice (0120/0121-0130)
(c) Reversal advice (0420/0421-0430)
Authorization advice transaction (0120/0121-0130) and Reversal Advice
(0420/0421-0430) are mandatory functions for Acquirer systems that have stand-in
authorization capability.
Figure 4-1 Message flow of authorization application

Licensee Licensee

0100
0110
::
::
0420
0430

04/01/2019 © 2019 JCB International All Rights Reserved Page 27

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 4 Online Applications

4.2 Record Registration/Inquiry Application

The record registration/inquiry application consists of the following transactions:
Record registration/inquiry request (0302-0312)
Issuers are required to choose either batch submission via EDI or online submission
for the negative data submission method.
Although negative data registration through the JCB Authorization Terminal can be
used together with online or batch submission, online and batch submission may not
be used in parallel by the same Issuer. Therefore, once a Licensee starts using
online submission of Negative File records, the batch transmission operation must be
discontinued.

Figure 4-2 Message flow of record registration/inquiry application

Issuer JCBI

0302
0312

The following types of requests are available:

• Add
• Revise
• Delete
• Inquiry
JCBI does not validate the request type strictly. That is, when JCBI receives a
request for revision and the card number does not exist in the Negative File, JCBI
processes the request as a request for an addition, for example. Depending on the
existence of the card number in Negative File, a request is processed as follows:

04/01/2019 © 2019 JCB International All Rights Reserved Page 28

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 4 Online Applications

Request Type Card number already exists in Process Result Response

Negative File? Code
Add No Record will be added 00
Yes Record will be revised 00
Revise No Record will be added 00
Yes Record will be revised 00
Delete No No operation 00
Yes Record will be deleted 00
Inquiry No Error 25
Yes Inquiry result will be returned 00

4.3 Summary of Application Features

The above-mentioned two types of online applications can exist together within a
single connection between the Licensee and J/Bridge. Figure 4-3 shows a
summary of transaction relations for each application type.
Figure 4-3 Transaction relations for each application type

Application 100 120 302 420 600

Authorization U U N U U
Record N N U N U
registration/inquiry

U: Used N: Not Used

100 authorization request transactions (100-110)

120 authorization advice transactions (120/121-130)
302 record registration/inquiry transactions (302-312)
420 reversal advice transactions (420/421-430)
600 administrative transactions (620-630)

Figure 4-3 is just an example of message types applied for a particular interface.
Contact a JCBI representative for full details on the actual interface specifications.

04/01/2019 © 2019 JCB International All Rights Reserved Page 29

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

5 Message Format
This chapter specifies the formatting requirements for all application message texts.

5.1 Bit Map Allocation Lists

This section lists the required bit map allocation for each message class. The
message lists are categorized according to message class instead of transaction class
since some messages, such as the reversal advice message, are used in various
transactions.

5.1.1 Abbreviations used in figures

The below abbreviations are used in the figures in this section to define bit map
requirements.

Abbreviation Description
M Mandatory data element
ME Mandatory echo, shall echo the same data as the
original message
MR Mandatory repeat, shall repeat the same data as the
original message
MS Mandatory reversal, shall contain the same data of the
original message
C Conditionally required
CE Conditional echo, shall echo the same data if the data
element exists in the original message
CR Conditional repeat, shall repeat the same data if the
data element exists in the original message
CS Conditional reversal, shall contain the same data of the
original message (this field is mandatory if it is
contained in the original message)
- Not mandatory but can be present
/ Must not be present; treated as a format error by the
message receiver
X JCB Brand system insert the data element
→ Forwarded and unchanged

04/01/2019 © 2019 JCB International All Rights Reserved Page 30

No. 100 110

Bit Map Description
ACQ JCB ISS ISS JCB ACQ
48 Additional data, private C → C CE → C
49 Currency code, transaction M → M ME → M
51 Currency code, cardholder billing / X M C → /
52 Personal identification number (PIN) data C X C / → /
53 Security related control information C X C / → /
54 Additional amounts C → C C → C
Integrated Circuit Card (ICC) System Related
55* C → C** C → C
Data
60 STIP Related Information / → / / / /
61 Point of Service Information M → M / → /
*: This is related to EMV transaction. Licensees must receive the prior approval of
JCBI if they plan to deal with ICC card.
**: This field is not sent to an Issuer when JCBI performs IC related authentications.
120 (ACQ) 120 (Brand)
No. Bit Map Description
ACQ JCB ISS ACQ JCB ISS
2 Primary account number M → M － M M
3 Processing code M → M － M M
4 Amount, transaction M → M － M M
6 Amount, cardholder billing / X M － M M
7 Transmission date and time M → M － M M
10 Conversion rate, cardholder billing / X M － M M
11 System trace audit number M → M － M M
12 Time, local transaction M → M － M M
13 Date, local transaction M → M － M M
14 Date, expiration C → C － C C
16 Date, conversion / X M － M M
18 Merchant’s type M → M － M M
22 Point of service entry mode M → M － M M

23* Card sequence number C → C － C C

25 Point of service condition code M → M － M M

04/01/2019 © 2019 JCB International All Rights Reserved Page 33

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

120 (ACQ) 120 (Brand)

No. Bit Map Description
ACQ JCB ISS ACQ JCB ISS
26 Point of service PIN capture code / → / － / /
28 Acquiring institution identification code C → C － C C
32 Acquiring institution identification code M → M － M M
33 Forwarding institution identification code M → M － M M
35 Track 2 data C → C － C C
37 Retrieval reference number M → M － M M
38 Authorization identification response C → C － C C
39 Response code M → M － M M
41 Card acceptor terminal identification C → C － C C
42 Card acceptor identification code C → C － C C
43 Card acceptor name and location M → M － M M
44 Additional response data C → C － C C
45 Track 1 data C → C － C C
48 Additional data, private C → C － C C
49 Currency code, transaction M → M － M M
51 Currency code, cardholder billing / X M － M M
52 Personal identification number (PIN) data / → / － / /
53 Security related control information / → / － / /
54 Additional amounts C → C － / /
Integrated Circuit Card (ICC) System Related
55* C → C** － C C
Data
60 STIP Related Information C → C － C C
61 Point of Service Information M → M － M M
*: This is related to EMV transaction. Licensees must receive the prior approval of
JCBI if they plan to deal with ICC card.
**: This field is not sent to an Issuer when the Issuer applies for IC Authentication
Service.

04/01/2019 © 2019 JCB International All Rights Reserved Page 34

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

121 (ACQ) 130 (to ACQ) 130 (to JCB)

No. Bit Map Description
ACQ JCB ISS JCB ACQ ISS JCB
2 Primary account number MR → M ME M ME M
3 Processing code MR → M ME M ME M
4 Amount, transaction MR → M ME M ME M
6 Amount, cardholder billing / X M / / CE C
7 Transmission date and time MR → M ME M ME M
10 Conversion rate, cardholder billing / X M / / CE C
11 System trace audit number MR → M ME M ME M
12 Time, local transaction MR → M CE C CE C
13 Date, local transaction MR → M ME M ME M
14 Date, expiration CR → C CE C CE C
16 Date, conversion / X M / / CE C
18 Merchant’s type MR → M / / / /
22 Point of service entry mode MR → M / / / /
23* Card sequence number CR → C / / / /
25 Point of service condition code MR → M / / / /
26 Point of service PIN capture code / → / / / / /
28 Amount, transaction fee CR → C CE C CE C
32 Acquiring institution identification code MR → M ME M ME M
33 Forwarding institution identification code MR → M ME M ME M
35 Track 2 data CR → C / / / /
37 Retrieval reference number MR → M ME M ME M
38 Authorization identification response CR → C CE C CE C
39 Response code MR → M ME M ME M
41 Card acceptor terminal identification CR → C / / / /
42 Card acceptor identification code CR → C CE C CE C
43 Card acceptor name and location MR → M / / / /
44 Additional response data CR → C CE C CE C
45 Track 1 data CR → C / / / /
48 Additional data, private CR → C C C CE C
49 Currency code, transaction MR → M ME M ME M
51 Currency code, cardholder billing / X M / / CE C
52 Personal identification number (PIN) data / → / / / / /
53 Security related control information / → / / / / /
04/01/2019 © 2019 JCB International All Rights Reserved Page 35
NOTE: This information, provided by JCBI, is confidential and proprietary and shall not be duplicated, published or
disclosed to any third party, in whole or in part, without the express written permission of JCBI.
Main Index

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

121 (ACQ) 130 (to ACQ) 130 (to JCB)

No. Bit Map Description
ACQ JCB ISS JCB ACQ ISS JCB

54 Additional amounts CR → C C C C C
Integrated Circuit Card (ICC)
55* CR → C** CE C CE C
System Related Data
60 STIP Related Information CR → C / / / /
61 Point of Service Information MR → M / / / /
*: This is related to EMV transaction. Licensees must receive the prior approval of
JCBI if they plan to deal with ICC card.
**: This field is not sent to an Issuer when the Issuer applies for IC Authentication
Service.

121 (Brand) 130 (to JCB)

No. Bit Map Description
ACQ JCB ISS ISS JCB
2 Primary account number － MR M ME M
3 Processing code － MR M ME M
4 Amount, transaction － MR M ME M
6 Amount, cardholder billing － MR M CE C
7 Transmission date and time － MR M ME M
10 Conversion rate, cardholder billing － MR M CE C
11 System trace audit number － MR M ME M
12 Time, local transaction － MR M CE C
13 Date, local transaction － MR M ME M
14 Date, expiration － CR C CE C
16 Date, conversion － MR M CE C
18 Merchant’s type － MR M / /
22 Point of service entry mode － MR M / /
23* Card sequence number － CR C / /
25 Point of service condition code － MR M / /
26 Point of service PIN capture code － / / / /
28 Amount, transaction fee － CR C CE C
32 Acquiring institution identification code － MR M ME M
33 Forwarding institution identification code － MR M ME M

04/01/2019 © 2019 JCB International All Rights Reserved Page 36

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

121 (Brand) 130 (to JCB)

No. Bit Map Description
ACQ JCB ISS ISS JCB
35 Track 2 data － CR C / /
37 Retrieval reference number － MR M ME M
38 Authorization identification response － CR C CE C
39 Response code － MR M M M
41 Card acceptor terminal identification － CR C / /
42 Card acceptor identification code － CR C CE C
43 Card acceptor name and location － MR M / /
44 Additional response data － CR C CE C
45 Track 1 data － CR C / /
48 Additional data, private － CR C / /
49 Currency code, transaction － MR M ME M
51 Currency code, cardholder billing － MR M CE C
52 Personal identification number (PIN) data － / / / /
53 Security related control information － / / / /
54 Additional amounts － CR C C C
Integrated Circuit Card (ICC) System
55* － CR C** CE C
Related Data
60 STIP Related Information － CR C / /
61 Point of Service Information － MR M / /
*: This is related to EMV transaction. Licensees must receive the prior approval of
JCBI if they plan to deal with ICC card.
**: This field is not sent to an Issuer when the Issuer applies for IC Authentication
Service.

5.1.3 Record Registration/Inquiry Message Class

The record registration/inquiry message class contains the following message types:
(a) Record registration/inquiry request (0302)
(b) Record registration/inquiry request response (0312)

04/01/2019 © 2019 JCB International All Rights Reserved Page 37

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Figure 5-2 Bit map fields –Record registration/inquiry message class

<J-Link 9>
No. Bit Map Description 0302 0312
1 Bit map, extended M M
7 Transmission date and time M ME
11 System trace audit number M ME
32 Acquiring institution identification code M ME
33 Forwarding institution identification code M ME
39 Response code / M
41 Card acceptor terminal identification C CE
63 Transaction code M ME
100 Receiving institution identification code C CE
101 File name M ME
120 Record data M M
127 Negative data access code M -

5.1.4 Reversal Message Class

The reversal message class contains the following message types:
(a) Reversal advice (0420)
(b) Reversal advice repeat (0421)
(c) Reversal advice response (0430)

Figure 5-3 Bit map fields -Reversal message class

<J-Link9>

420 (ACQ) 430 (to ACQ) 430 (to JCB)

No. Bit Map Description
ACQ JCB ISS JCB ACQ ISS JCB
1 Bit map, extended M → M M M M M
2 Primary account number MS → MS ME M ME M
3 Processing code MS → MS ME M ME M
4 Amount, transaction MS → MS ME M ME M
6 Amount, cardholder billing / X M / / CE C
7 Transmission date and time MS* → MS ME M ME M
10 Conversion rate, cardholder billing / X M / / CE C
11 System trace audit number MS* → MS ME M ME M
12 Time, local transaction MS* → MS CE C CE C
04/01/2019 © 2019 JCB International All Rights Reserved Page 38
NOTE: This information, provided by JCBI, is confidential and proprietary and shall not be duplicated, published or
disclosed to any third party, in whole or in part, without the express written permission of JCBI.
Main Index

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

420 (ACQ) 430 (to ACQ) 430 (to JCB)

No. Bit Map Description
ACQ JCB ISS JCB ACQ ISS JCB
13 Date, local transaction MS* → MS ME M ME M
16 Date, Conversion / X M / / CE C
22 Point of service entry mode MS* → MS / / / /
23** Card sequence number CS → CS / / / /
25 Point of service condition code MS* → MS / / / /
28 Amount, transaction fee CS → CS CE C CE C
32 Acquiring institution identification code MS* → MS ME M ME M
33 Forwarding institution identification code MS* → MS ME M ME M
37 Retrieval reference number MS → MS ME M ME M
38 Authorization identification response CS → CS / / / /
39 Response code M → M M M M M
42 Card acceptor identification code CS → CS CE C CE C
43 Card acceptor name and location MS → MS / / / /
44 Additional response data / → / / / / /
49 Currency code, transaction MS → MS ME M ME M
51 Currency code, cardholder billing / X M / / CE C
54 Additional amounts / → / / / / /
90 Original data elements M → M ME M ME M
95 Replacement amounts M X M ME M ME M
* : It is recommended for Acquirers to set the same value as the original message in
these bits. JCBI does not check if these bits have the same values as the original
message. Thus, it is NOT recommended for Issuers to use these bits as matching
keys in reversal processing since they are not guaranteed to have the same value.
It is recommended that matching keys be selected from bits designated as ‘MS’ in
the above chart and the sub fields in bit 90.
**: This is related to EMV transaction. Licensees must receive the prior approval of
JCBI if they plan to deal with IC card.

420 (JCB) 430 (to JCB)

No. Bit Map Description
ACQ JCB ISS ISS JCB
1 Bit map, extended / M M M M
2 Primary account number / MS MS ME M

04/01/2019 © 2019 JCB International All Rights Reserved Page 39

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

3 Processing code / MS MS ME M
4 Amount, transaction / MS MS ME M
6 Amount, cardholder billing / M M CE C
7 Transmission date and time / MS* MS ME M
10 Conversion rate, cardholder billing / M M CE C
11 System trace audit number / MS* MS ME M
12 Time, local transaction － MS* MS CE C
13 Date, local transaction / MS* MS ME M
16 Date, Conversion / M M CE C
22 Point of service entry mode / MS* MS / /
23** Card sequence number － CS CS / /
25 Point of service condition code / MS* MS / /
28 Amount, transaction fee / CS CS CE C
32 Acquiring institution identification code / MS* MS ME M
33 Forwarding institution identification code / MS* MS ME M
37 Retrieval reference number / MS MS ME M
38 Authorization identification response / → / / /
39 Response code / M M M M
42 Card acceptor identification code / CS CS CE C
43 Card acceptor name and location / MS MS / /
44 Additional response data / → / / /
49 Currency code, transaction / MS MS ME M
51 Currency code, cardholder billing / M M CE C
54 Additional amounts / → / / /
90 Original data elements / M M ME M
95 Replacement amounts / M M ME M
* It is recommended for Issuers that matching keys be selected from bits designated
as ‘MS’ in the above chart and the sub fields in bit 90.
**: This is related to EMV transaction. Licensees must receive the prior approval of
JCBI if they plan to deal with IC card.

04/01/2019 © 2019 JCB International All Rights Reserved Page 40

System Specifications – Online Interface Guide
Chapter 5 Message Format

5.1.6 Network Management Message Class

The network management message class contains the following message types:
(a) Network management request (0800)
(b) Network management request response (0810)

Figure 5-5 Bit map fields -Network control message class

<J-Link 9>
No. Bit Map Description 0800 0810
1 Bit map, extended M M
7 Transmission date and time M ME
11 System trace audit number M ME
33 Forwarding institution identification code M ME
39 Response code / M
53 Security related control information C C
70 Network management information code M ME
96 Message security code for Single DES C /
100 Receiving institution identification code M ME
105 Message security code for Triple DES C /

 NOTE : In case of Dynamic Key Exchange, Bit 96 or Bit 105 will be added in 0800 message.
Before the start of programming or implementation of Dynamic Key Exchange in the
Licensee’s system, the details of the specifications should be discussed and agreed upon by the
Licensee and JCBI.

5.2 Data Elements of J-Link9

The data elements used in J-Link9 correspond to those defined in ISO 8583:1987.
Data elements described as ‘not supported’ in the following list cannot exist in the
application message, and J-Link9 does not guarantee processing or forwarding of
them. Moreover, data elements which are not defined in the list are invalid in
J-Link9. If a message contains such an undefined element, the message will be
considered to have a format error. If any unsupported data elements are required,
they are to be confirmed with JCBI by using the specification exception form, as
stipulated by the J-Link9 certification procedures.

04/01/2019 © 2019 JCB International All Rights Reserved Page 43

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Primary bit map

Length 64 bits
Format Bit string
Description The primary bit map indicates the existence of data elements for the first 64 fields, and is
mandatory for all message types.

Bit 1 Secondary bit map

Length 64 bits
Format Bit string
Description The secondary bit map indicates the existence of data elements from bit 65 to bit 128.

Bit 2 Primary account number (PAN)

Length 1 binary byte, then up to 19 digits (maximum of 11 bytes)
Format LLVAR binary, numeric 4-bit BCD (unsigned, packed)
Description Consists of two sub-fields: length (8 bits), and the PAN itself (maximum of 19 digits).
A leading zero padding is required to fill the PAN, which consists of an odd number of
digits.

X’10 3540 0000 0000 0000’

Length sub-field PAN sub-field

1 byte (binary) max. 10 bytes or 19 digits (variable length)

04/01/2019 © 2019 JCB International All Rights Reserved Page 44

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 3 Processing code

Length 6 digits, 3 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description This field is used to describe the effect of a transaction on the customer account and
the type of accounts affected.

Position 1-2: Transaction Code

00: Purchase

01: Withdrawal / Cash Advance（including Manual Cash Advance）

30: Balance Inquiry

Position 3-4: Cardholder Account Type (From)

00: No account specified

10: Saving Account

20: Checking Account

30: Credit Account

Position 5-6: Cardholder Account Type (To)

00: No account specified/ Not applicable

Note
 Acquirers can initiate Balance Inquiry function by setting the value of 30 in
position 1-2. However, Balance Inquiry transactions are not sent to the issuer
and are returned as error transactions when the issuer does not support
J-Link9 or the transaction function.

04/01/2019 © 2019 JCB International All Rights Reserved Page 45

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 4 Amount, transaction

Length 12 digits, 6 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description The total amount of the transaction per the currency code in bit 49.
*This field must include the surcharge amount if the Merchant imposes a surcharge.
*This field must include the amount in bit 28 (Amount, transaction fee), if bit 28 exists.

*For Partial Approvals in the #0110 message, an Issuer shall set the original amount. (The
Issuer shall set the Partial Approval amount in Bit 6.) An Acquirer will receive the Partial
Approval amount in this field from JCB.

*For Partial Approval reversals in the #0420 message, an Acquirer shall set the Partial
Approval amount from the #0110 message, if the Acquirer has received a #0110
message. An Issuer will receive the original amount in this field from JCB. (The Issuer will
receive the Partial Approval amount in Bit 6.)
*For Balance Inquiry in the #0100 message, an Acquirer shall set zero amount in this field.
*For DCC transaction in the #0100/#0110 and #0120/0130 message, this field contains the
amount in cardholder billing currency .

The decimal place rules are based on ISO4217:1987. Leading zeros are required to pad
the leftover digits since this is a 12-digit fixed length field.

Note
 ATM Access Fee is allowed for Acquirer which obtained prior approval from
JCBI.

Bit 5 Amount, reconciliation

Length 12 digits, 6 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description Not supported

04/01/2019 © 2019 JCB International All Rights Reserved Page 46

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 6 Amount, cardholder billing

Length 12 digits, 6 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description The total amount of the transaction per the issuer's currency.
bit 6 = bit 4 (Amount, Transaction) x bit 10 (Conversion rate, cardholder billing)

*For Partial Approvals in the #0110 message, an Issuer shall set the Partial Approval
amount in this field.
*For Partial Approval reversals in the #0420 message, an Issuer will receive the Partial
Approval amount in this field.

Bit 7 Transmission date and time (Greenwich mean time)

Length 10 digits, 5 bytes
Format Numeric 4-bit BCD (unsigned, packed, MMDDhhmmss)
Description This field is used to identify each transaction, and must be contained in bit 90 (original data
element) of the 0420 reversal advice message in order to identify the original transaction to
be reversed.

Bit 8 Amount, cardholder billing fee

Length 8 digits, 4 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description Not supported

Bit 9 Conversion rate, settlement

Length 8 digits, 4 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description Not supported

04/01/2019 © 2019 JCB International All Rights Reserved Page 47

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 10 Conversion rate, cardholder billing

Length 8 digits, 4 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description This field is used in the conversion from transaction to cardholder billing amount.
An Issuer shall echo the value in #0110 message if bit 6 is present.
If bit 49 (Currency code, transaction) and bit 51 (Currency code, cardholder billing) are the
same, no conversion is performed by JCBI and this field is set to 1.

Bit 11 System trace audit number

Length 6 digits, 3 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description This field contains the audit number used to identify the transaction. This field must be
contained in bit 90 (original data element) of the 0420 reversal advice message in order to
identify the original transaction to be reversed.

Bit 12 Time, local transaction

Length 6 digits, 3 bytes
Format Numeric 4-bit BCD (unsigned, packed, hhmmss)
Description The local time at which the transaction takes place at the card acceptor location.

Bit 13 Date, local transaction

Length 4 digits, 2 bytes
Format Numeric 4-bit BCD (unsigned, packed, MMDD)
Description The local date on which the transaction takes place at the card acceptor location

Bit 14 Date, expiration

Length 4 digits, 2 bytes
Format Numeric 4-bit BCD (unsigned, packed, YYMM)
Description This field is required when neither bit 35 (track 2 data) nor bit 45 (track 1 data) are present.
This field is forwarded to an Issuer only when it is received from an Acquirer.

Bit 15 Settlement date

Length 4 digits, 2 bytes
Format Numeric 4-bit BCD (unsigned, packed, MMDD)
Description Not supported

04/01/2019 © 2019 JCB International All Rights Reserved Page 48

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 16 Date, conversion

Length 4 digits, 2 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description This field contains the effective date of bit 10 (Conversion rate, cardholder billing).
Format : MMDD
An Issuer shall echo the value in #0110 message if bit 6 is present.

Bit 17 Date, capture

Length 4 digits, 2 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description Not supported

Bit 18 Merchant’s type

Length 4 digits, 2 bytes
Format Numeric 4-bit BCD (unsigned, packed)
Description Contains a Merchant Category Code to identify a Merchant’s type of business as specified
in Code List.

Bit 19 Country code, acquiring institution

Length 3 digits, 2 bytes

Format Numeric 4-bit BCD (unsigned, packed)

Description Not supported

Bit 20 Country code, primary account number

Length 3 digits, 2 bytes

Format Numeric 4-bit BCD (unsigned, packed)

Description Not supported

Bit 21 Country code, forwarding institution

Length 3 digits, 2 bytes

Format Numeric 4-bit BCD (unsigned, packed)

Description Not supported

04/01/2019 © 2019 JCB International All Rights Reserved Page 49

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 22 Point of service entry mode

Length 4 digits, 2 bytes

Format Numeric 4-bit BCD (unsigned, packed)

Description Indicates the PAN entry method and PIN entry capability.

Positions 1 and 2: PAN entry mode

X'00' Unknown
X'01' Manual entry (typing)
X'02' Magnetic stripe reading

X'05'* Chip reading

X’07'* Contactless EMV mode
X'81' Electronic Commerce
X’91’* Contactless magnetic stripe mode
X'97'* Magnetic stripe reading
(This value is set when chip-capable terminal was unable
to read a Chip Card, therefore the terminal read the magnetic stripe.)
Position 3: PIN entry capability
X'0' Unknown
X'1' Terminal can accept PINs
X'2' Terminal cannot accept PINs

Position 4: X'0' reserved

*: This is related to EMV transaction. Licensees must receive the prior approval of JCBI if
they plan to handle IC card transactions.

 NOTE: This data element is subject to validation by JCBI and Issuers. An

Acquirer must set appropriate value.

04/01/2019 © 2019 JCB International All Rights Reserved Page 50

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 23 Card sequence number

Length 4 digits, 2 bytes

Format Numeric 4-bit BCD (unsigned, packed)

Description* Distinguishes between two or more separate cards having the same PAN.

If bit 55 is present, and the Application PAN Sequence Number (EMV tag 5F34**) is stated
in the ICC, the Acquirer must pad this number with two leading zeros and set the value
in bit 23.
Ex. If EMV tag 5F34 = ’01’ then bit 23 = ‘0001’
If tag 5F34 is not available, bit 23 will not be provided to an Issuer.
If bit 55 is not present, bit 23 will not be provided to an Issuer.
*: This is related to EMV transaction. Licensees must receive the prior approval of JCBI if
they plan to handle IC card transactions.
**: Tag 5F34 is not included in Bit 55.

Bit 24 Network international identifier

Length 3 digits, 2 bytes

Format Numeric 4-bit BCD (unsigned, packed)

Description Not supported

04/01/2019 © 2019 JCB International All Rights Reserved Page 51

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 25 Point of service condition code

Length 2 digits, 1 bytes

Format Numeric 4-bit BCD (unsigned, packed)

Description

Identifies conditions under which the transaction takes place at the point of service. The value must be one of
those listed in the following table:

Code Meaning Code Meaning

00 Normal presentment 14 Public utility terminal

01 Cardholder not present 15 Cardholder (home) terminal

02 Unattended terminal able to retain card 16 Administration terminal

03 Merchant suspicious 17 Returned item (chargeback)

04 Electronic cash register interface 18 No cheque in envelope/all returned

05 Cardholder present, card not present 19 Deposit out-of-balance/all returned

06 Pre-authorized request 20 Payment out-of-balance/all returned

07 Telephone device request 21 Manual reversal

08 Mail and/or telephone order 22 Terminal error/counted

09 Security alert 23 Terminal error/not counted

10 Cardholder identity verified 24 Deposit out-of-balance/applied contents

11 Suspected fraud 25 Payment out-of-balance/applied contents

12 Security reasons 26 Withdrawal had error/reversed

13 Representation of item 27 Unattended terminal unable to retain card

 NOTE : Code 06 Pre-authorized request is only allowed for hotel and rent-a-car Merchants. 

Bit 26 Point of service PIN capture code

Length 2 digits, 1 bytes

Format Numeric 4-bit BCD (unsigned, packed)

Description Contains the maximum number of PIN characters which the terminal can accept. This field
is mandatory if bit 52 exists.

Bit 27 Authorization identification response length

Length 1 digit, 1 byte

Format Numeric 4-bit BCD (unsigned, packed)

Description Not supported

04/01/2019 © 2019 JCB International All Rights Reserved Page 52

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 28 Amount, transaction fee

Length 1 character indicating debit or credit, followed by 8 digits

Format 1 character and numeric characters (EBCDIC)

Description This field contains ATM Access Fee charged by the acquirer for ATM transactions in the
currency of bit 4 (Amount transaction).
For Balance Inquiry transactions, the Acquirer shall not charge ATM Access Fee.
For Partial Reversal transactions, this field contains ATM Access Fee amount of bit 95
subfield 1 (Actual Amount, Transaction) in the #0420 message. This fee can be less
amount than the fee for the original transaction.

Position 1:
Indicates whether the amount is credit or debit
C = Credit
D = Debit

Position 2-9:
Indicates the fee amount in the currency of bit 4 (Amount, Transaction).

Bit 29 Amount, settlement fee

Length 1 character indicating debit ('D') or credit ('C'), followed by 8 digits

Format 1 character and numeric 4-bit BCD (unsigned, packed)

Description Not supported

Bit 30 Amount, transaction processing fee

Length 1 character indicating debit ('D') or credit ('C'), followed by 8 digits

Format 1 character and numeric 4-bit BCD (unsigned, packed)

Description Not supported

Bit 31 Amount, settlement processing fee

Length 1 character indicating debit ('D') or credit ('C'), followed by 8 digits

Format 1 character and numeric 4-bit BCD (unsigned, packed)

Description Not supported

04/01/2019 © 2019 JCB International All Rights Reserved Page 53

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 32 Acquiring institution identification code

Length 1 binary byte, then up to 11 digits (maximum of 7 bytes)

Format LLVAR binary, numeric 4-bit BCD (unsigned, packed)

Description 0100/0420
Contains the ID of the acquiring institution sending an authorization request. Values must
be defined under bilateral agreement in accordance with the J-Link certification procedures.

0302
Contains the ID of the initiator of the record registration/inquiry request.

Bit 33 Forwarding institution identification code

Length 1 binary byte, then up to 11 digits (maximum of 7 bytes)

Format LLVAR binary, numeric 4-bit BCD (unsigned, packed)

Description Contains the ID of the institution forwarding a request or advice message. Values must be
defined under bilateral agreements in accordance with the J-Link certification procedures.

Bit 34 Primary account number, extended

Length 1 binary byte, then up to 28 digits (maximum of 15 bytes)

Format LLVAR binary, numeric 4-bit BCD (unsigned, packed)

Description Not supported

Bit 35 Track 2 data

Length 1 binary byte, then up to 37 digits

Format LLVAR binary, numeric 4-bit BCD and hexadecimal, as defined in ISO 7811/2

Description Contains the data encoded in track 2 of the magnetic stripe as defined in ISO 7813. When
the data consists of an odd number of digits, a leading zero is required to pad the first
unused half-byte of data. This field is required if PAN entry mode in bit 22 (point of service
entry mode) indicates X'02', X'05'(*), X’07’(*), X’91’(*) or X'97'(*).
* For chip transactions, bit 35 shall contain track 2 equivalent data.

When the Track 2 data is present, an Acquirer shall send only Track 2 data.
(Track 1 data (Bit 45) is only sent for POS transactions when the Track 2 data is not
present.)

*: This is related to EMV transaction. Licensees must receive the prior approval of JCBI if
they plan to handle IC card transactions.

04/01/2019 © 2019 JCB International All Rights Reserved Page 54

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 36 Track 3 data

Length 1 binary byte, then up to 104 positions (maximum of 55 bytes).

Format LLVAR binary, numeric 4-bit BCD and hexadecimal, as defined in ISO 7811/2

Description Contains the data encoded in track 3 of the magnetic stripe as defined in ISO 7813.
J-Link does not use this element.

Bit 37 Retrieval reference number

Length 12 digits, 12 bytes

Format Alphabetic, numeric characters and space (EBCDIC)

Description The reference number supplied by the Acquirer, which is used to identify the original
message and the original source document.

Bit 38 Authorization identification response

Length 6 digits, 6 bytes

Format Alphabetic and numeric characters (EBCDIC)

Description 0110
This field contains the string identifying the response from the authorizing institution when a
cardholder transaction is being approved. When an Issuer sets the value of ‘85’ in Bit 39
(Response Code), this field shall be set as '000000'

0420
This field must echo the original value of 0110 when available.

Bit 39 Response code

Length 2 digits, 2 bytes

Format Alphabetic and numeric characters (EBCDIC)

Description In response messages, this field contains the response to the Issuer application or JCBI for
the corresponding request or advice message. In advice messages, this field contains the
reason for the advice initiation.
For Balance Inquiry and AVS only transaction, an Issuer shall set the value of ‘00’ or ‘85’
Refer to Appendix OIG-1.

Bit 40 Service restriction code

Length 3 digits, 3 bytes

Format Alphabetic and numeric characters (EBCDIC)

Description Not supported

04/01/2019 © 2019 JCB International All Rights Reserved Page 55

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 41 Card acceptor terminal identification code

Length 8 digits, 8 bytes

Format Alphabetic, numeric characters and special characters (EBCDIC)

Description 0100
An identification code of 8 characters or less for the card acceptor terminal. The Acquirer
has the responsibility of maintaining the editing rules for this field. This field must be
left-justified with trailing blanks. JCBI recommends it be used.

0302
An identification code of 8 characters or less for the record registration/inquiry request
initiator. This value must be agreed upon by both parties in accordance with the J-Link
certification procedures.

Bit 42 Card acceptor identification code

Length 15 digits, 15 bytes

Format Alphabetic, numeric, and special characters (EBCDIC)

Description An identification code for the card acceptor, of 15 characters or less. The Acquirer has the
responsibility of maintaining the editing rules for this field. This field must be left-justified
with trailing blanks. JCBI recommends it be used.

04/01/2019 © 2019 JCB International All Rights Reserved Page 56

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 43 Card acceptor name and location

Length 40 characters

Format Alphabetic, numeric, and special characters (EBCDIC)

Description This field contains the name and location of the card acceptor.

Positions 1-22:
Merchant Name or the ATM location, branch number, or street address
For Payment Facilitator Transactions, set the Payment Facilitator name and
Sub-merchant name using the following format:
Payment Facilitator name @ Sub-merchant name
or
Payment Facilitator name * Sub-merchant name

 NOTE: Use the same Sub-merchant name displayed on the storefront or order
page.

 NOTE: If there is not enough space, use the abbreviated name of the Payment
Facilitator applied for in advance using Appendix 4-34.

Position 23:
Space

Positions 24-36:
Merchant or ATM Location City

Position 37:
Space

Positions 38-40:
Country Code (alphabetic)

Note JCB will send this field space-filled when JCB does not receive the information from an
Acquirer

04/01/2019 © 2019 JCB International All Rights Reserved Page 57

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 44 Additional response data

Length 1 binary byte, then up to 99 bytes

Format LLVAR binary, Alphabetic, numeric, and special characters (EBCDIC)

Description This field contains CAV2 verification result code and/or AVS result code (bit 48). Must be
present in authorization request response if either CAV2 (bit 48 tag 01) or AVS Data (bit
48 tag 03) is present in the #0100 message.

Byte 1 Byte 2 Byte 3

CAV2 Result AVS Result
Length
Code Code

Byte 1:
Value must be X’02’ if either CAV2 (bit 48 tag 01) or AVS Data (bit 48 tag 03) is present in
#0100 message.

Byte 2: Possible values:

M: CAV2 match
N: CAV2 no match
P: CAV2 not processed
S: CAV2 should be on card
U: Issuer does not participate in CAV2 service
(space): CAV2 was not provided

Byte 3: Possible values:

A: Street address matches, postal code does not
D: Street address matches and postal codes match
G: Address information not verified for international transactions
I: Address information not verified
N: Neither address or postal code matches
P: Postal code matches, street address not verified because of incompatible formats
U: No data from Issuer
(space): AVS Data was not provided.

Note CAV2 and AVS verification results are not forwarded to the acquirer when the acquirer or
the issuer does not support J-Link9 or the authentication function.

04/01/2019 © 2019 JCB International All Rights Reserved Page 58

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 45 Track 1 data

Length 1 binary byte, then up to 76 bytes

Format LLVAR binary, Alphabetic, character (alphabetic, numeric, and special) string

Description Contains the data encoded in track 1 of the magnetic stripe as defined in ISO 7813.

ATM transactions must have Track 2 data (Bit 35). This Bit should not be sent. This Bit is
only sent for POS transactions when the Track 2 data is not present.

Bit 46 Additional data, ISO

Length 1 binary byte, then up to 76 bytes

Format LLVAR binary, character (alphabetic, numeric, and special) string, as defined in ISO 7811/2

Description Not supported

Bit 47 Additional data, national

Length 1 binary byte, then up to 255 characters

Format LLVAR binary, numeric and character (can be binary data) string

Description Not supported

04/01/2019 © 2019 JCB International All Rights Reserved Page 59

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 48 Additional data, private

Length 1 binary byte, then up to 255 characters

Format LLVAR binary

Description This data element is used for both the authorization messages (01xx) and the administrative
advice message (0620).
Administrative advice message (0620, used only for unrecognized message indication)
Bit 48 contains the raw data from the unrecognized message; the original unrecognized
message must be truncated if its length is 256 bytes or greater.

Bit 48 Data Layout

Message length Unrecognized message

Authorization messages (0100,0120,0121)

The total Bit 48 length is specified in its first byte, followed by each sub-element that begins
with a two-byte tag and an associated two-byte length indicator.

Bit 48 Data Layout

Total length of 1st sub-field 2nd sub-field … Nth sub-field

this field (Bit48) Tag Length Valu Tag Length Valu Tag Length Valu

e e e

Bit 48 Sub-field

Description Tag Length Comments Message

CAV2 01 03 This value is indent printed on the card’s 0100

signature panel. If the data does not 0120
exist, this tag should not be generated. 0121

3-D Secure 02 47 This tag is set for the messages 0100

/ In-App originated 0120
Transaction from the merchants participating in 3-D 0121
Secure or In-App Transactions.
If this tag exists, PAN entry mode in bit 22
(point of service entry mode) should be
X’01’ or X’81’.
If all values (XID, CAVV, and ECI) do not
exist, this tag should not be generated.

04/01/2019 © 2019 JCB International All Rights Reserved Page 60

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Address 03 14 Position 1-9 0100

verification Postal Code: An Acquirer shall set the 0120
service data value left justified and space-filled. 0121

 NOTE: An Issuer might receive

this value with zero-filled.
Position 10-14
Street Address: Up to first 5 numeric
digits of street address, left justified with
space filled.

 NOTE: An Issuer might

receive this data with
transaction amount (Bit 4) of
zero.(Called AVS only
transaction)

POS Data, 04 01 The value indicates Terminal Capability of 0100

Extended Partial Approval. 0120
Condition This tag must be set when an Acquirer 0121
Code receives the Partial Approval capability
information from the merchant terminal.
If the merchant terminal supports Partial
Approvals, then set ’1’.
If the merchant terminal does not support
Partial Approvals, then set ’0’.

 NOTE: Partial Approval shall

be used only for the purchase
transaction. It shall not be
used for the ATM transaction.

04/01/2019 © 2019 JCB International All Rights Reserved Page 61

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 48 “Additional data, private” continues:

Detailed Layout of 3-D Secure Value (Tag 02)

Field description Format

XID XID (Transaction Identifier) is an unique number 4bit HEX

generated by Merchant to identify the transaction. 20 bytes
If the value is Base64-encoded, which is a 28 byte value,
it must be decoded into a 20 byte binary value prior to
submission to JCB. If the value does not exist, the field
should be filled with spaces (X’40’).
For J/Secure2.0 transactions, XID is not required.

CAVV CAVV (Cardholder Authentication Verification Value) is a 4bit BCD

cryptographic value calculated by ACS (Access Control 20 bytes
Server) using the issuer’s encryption key and related
elements.
If the value is Base64-encoded, which is a 28 byte value,
it must be decoded into a 20 byte binary value prior to
submission to JCB. If the value does not exist, the field
should be filled with spaces (X’40’).

ECI ECI (Electronic Commerce Indicator) 4bit BCD

‘05’: 3-D Secure authenticated Transaction 1 byte
‘06’: Merchant attempted to receive 3-D Secure
authentication, and authentication failed due to
Issuer or cardholder non-participation for 3-D
Secure.
‘07’: Unauthenticated Secured Transaction
If the value does not exist, the field should be filled with
spaces (X’40’).

Reserved (filled with spaces (X’40’)) 6 bytes

04/01/2019 © 2019 JCB International All Rights Reserved Page 62

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 48 “Additional data, private” continues:

Detailed Layout of In-App (Regular) Transaction Value (Tag 02)

Field description Format

XID Filled with spaces 4bit HEX

20 bytes

CAVV Set cryptogram received from applet. 4bit BCD

*If the value is Base64-encoded, which is a 28 byte value, 20 bytes
it must be decoded into a 20 byte binary value prior to
submission to JCB.

ECI Set value (=“05”) received from applet. 4bit BCD

If there is no ECI value, IPSP/Acquirer sets "05". 1 byte

Reserved (filled with spaces (X’40’)) 6 bytes

 NOTE: For In-App (Recurring) Transaction, Bit 48 Tag 02 is optional to be set.

Note An Acquirer must send CAV2 data to an Issuer when it is sent from a merchant.
Tag 03 and Tag 04 in Bit 48 are not forwarded to the issuer who does not support J-Link9.

04/01/2019 © 2019 JCB International All Rights Reserved Page 63

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 49 Currency code, transaction

Length 3 digits, 3 bytes

Format EBCDIC characters

Description Defines the currency of Bit 4 (Amount, transaction).

For DCC transaction, this field contains the currency code of cardholder billing currency..
Three-digit numeric currency code defined in Code List.

Bit 50 Currency code, settlement

Length 3 digits, 3 bytes

Format EBCDIC characters

Description Not supported

Bit 51 Currency code, cardholder billing

Length 3 digits, 3 bytes

Format EBCDIC characters

Description Defines the currency of bit 6 (Amount, Cardholder Billing).

Three-digit numeric currency code defined in Code List.
An Issuer shall echo the value in #0110 message if bit 6 is present.

Bit 52 PIN data

Length 64 bits

Format Numeric, bit string

Description The format of this field matches the PIN block format code in the security related control
field (bit 53).

04/01/2019 © 2019 JCB International All Rights Reserved Page 64

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 53 Security related control information

Length 16 digits, 8 bytes

Format Numeric 4-bit BCD (unsigned, packed) and hexadecimal

Description This field contains the check digits for the key; the last 8 bits are unused. The check digits
are the four leftmost digits of a zero PIN block encrypted with a key (with a new key in case
of 0800 message). This element is required in a 0100 message which contains bit 52 (PIN
data) and in a 0800 message with a network management information code of X'0101' (key
change). The format of this field is as follows;

Positions 1 and 2: Key Type

X'99' Acquirer and Issuer working key
Positions 3 and 4: PIN Encryption Algorithm
X'01' DES or Triple DES (Double length key)
Positions 5 and 6: PIN Block Format
X'01' ANSI Standard (ISO 9564-1 Format 0)
Positions 7 and 8: Key Index
X'00' not specified
Positions 9 and 10: MAC Index
X'00' not specified
Positions 11,12,13 and 14: Check Digits (16 bits, 2 bytes)
Positions 15 and 16: X’00’ reserved

04/01/2019 © 2019 JCB International All Rights Reserved Page 65

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 54 Additional amounts

Length 1 binary byte, then up to 120 characters

Format LLVAR binary, numeric and character (can be a binary data) string

Description This field provides information on up to six sets of Account Type, Amount type Currency
Code, Credit or Debit Sign and Amount .
This field will be used for Balance Inquiry, Partial Approval and DCC transaction.
For Balance Inquiry and Partial Approval, Bit 54 will be present in the #0110 message.
For DCC transaction, Bit 54 will be present in the #0100/#0110 and #0120/#0130 message.

Subfield 1 / Positions 1-2: Account Type

For Balance Inquiry and Partial Approval, this field contains the cardholder’s account type
as defined in bit 3 position 3-4 (Processing Code / Cardholder Account Type).
For DCC transaction, this field contains the two-digit code that is the same value as bit 3
position 3-4 (Processing Code / Cardholder Account Type).

Subfield 2 / Positions 3-4: Amount Type

This field indicates the type of amount applied.
01 = Ledger Balance (Only used for Balance Inquiry)
02 = Available Balance (Only used for Balance Inquiry)
57 = Original Amount (Only used for Partial Approval)
58= DCC Original Amount (Only used for DCC Transaction)

Subfield 3 / Positions 5-7: Currency Code

For Balance Inquiry transaction, an Issuer shall set Cardholder billing currency code
(same as Bit51) and an Acquirer will receive Transaction currency code (same as Bit 49)
from JCB. (3-digit numeric code)
For Partial Approval transaction, this field contains Transaction currency code (same as
Bit 49). (3-digit numeric code)
For DCC transaction, this field contains original local currency code (different from Bit 49
or Bit 51). (3-digit numeric code)

Subfield 4 / Position 8: Credit or Debit Sign

This field contains the credit or debit sign.
C = Credit amount
D = Debit amount

04/01/2019 © 2019 JCB International All Rights Reserved Page 66

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Subfield 5 / Position 9-20: Amount

Indicates the amount specified in Subfield 2 and the currency is as defined in Subfield 3..

Note -Bit 54 is not forwarded to the acquirer when the issuer does not support J-Link9.
-For Partial Approval reversals, Bit 54 shall not be used.
-DCC information may not be included in this field, depending on the authorization network
between JCB and the acquirer.

04/01/2019 © 2019 JCB International All Rights Reserved Page 67

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 55* Integrated Circuit Card ICC System Related Data

Length 2 binary bytes, then up to 255 bytes

Format LLLVAR binary (2 bytes : 0000 – 00FF)

Description

Contains the data on the chip captured by an IC card compliant POS terminal and ATM.
It is used for various processing by an Issuer and the IC card, such as card authentication, Issuer
authentication, and issuer script.

 NOTE: When JCBI performs IC related authentications on behalf of an Issuer, this field is not forwarded to
the Issuer. This includes all IC Cirrus ATM Transactions, since JCBI performs the authentications for them.

 NOTE: Chip data must be set according to the format of the EMV specification, which places the value in the
order of the “tag-length-value” series format as shown below.

Data Layout:

Total length of 1st sub-field 2nd sub-field ….. Nth sub-field

this field (Bit 55) Tag Length Value Tag Length Value Tag Length Value

1. Tag
Contains the tag value indicating the EMV data element as specified in the EMV ’96 specification.
(Binary representation, 1 byte to 2 bytes)
Refer to next page for details of “Tag” information.
2. Length
Contains the length in bytes of the following “Value”.
(Binary representation, 1 byte)
3. Value
Contains the data as defined in each tag data specification.
(Binary representation, 1 byte to 128 bytes)

 NOTE: Sub-fields should be generated until all IC chip data has been read.
JCBI will transfer the data set in bit 55 between an issuer and an acquirer without editing any of the data.

04/01/2019 © 2019 JCB International All Rights Reserved Page 68

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

The table below lists the mandatory and conditional sub-elements that an acquirer must or may set in bit 55 of
an authorization request message (#0100).

Bit 55 Sub-elements in Authorization Request Messages (#0100)

Description Tag Length of Value Comments

Application Cryptogram (AC) 9F26 8 Mandatory

Cryptogram Information Data 9F27 1 Mandatory

Issuer Application Data (IAD) 9F10 Variable (…32) Mandatory

Unpredictable Number 9F37 4 Mandatory

Application Transaction Counter 9F36 2 Mandatory

Terminal Verification Result (TVR) 95 5 Mandatory

Transaction Date 9A 3 Mandatory

Transaction Type 9C 1 Mandatory

Amount, Authorized 9F02 6 Mandatory

Transaction Currency Code 5F2A 2 Mandatory

Application Interchange Profile 82 2 Mandatory

Terminal Country Code 9F1A 2 Mandatory

Amount, Other 9F03 6 Mandatory

04/01/2019 © 2019 JCB International All Rights Reserved Page 69

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 55 Sub-elements in Authorization Request Messages (#0100) continued

Description Tag Length of Value Comments

Cardholder Verification Method 9F34 3 Conditional

(CVM) Results

Terminal Type 9F35 1 Conditional

Terminal Application Version 9F09 2 Conditional

Number

Terminal Capabilities 9F33 3 Conditional

Interface Device (IFD) Serial 9F1E 8 Conditional

Number

ICC Application ID 4F Variable (…16) Conditional

Transaction Sequence Counter 9F41 Variable (…4) Conditional

Dedicated File Name 84 Variable (…16) Conditional

 NOTE: The hexadecimal representation of the Tag is given above.

Every two positions of hexadecimal data equals one byte of binary data.
*An Acquirer must send conditional tags to an Issuer when they are sent from the terminal.
*The Amount, Authorized value (tag 9F02) may be different from the value set in Bit4 (Amount, transaction) of
the authorization request message. When using a transaction amount for the AC verification, Issuers are
advised to use the value in tag 9F02 of Bit 55, not in Bit 4.

04/01/2019 © 2019 JCB International All Rights Reserved Page 70

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

The table below lists the conditional sub-elements that an issuer may set in bit 55 of
an authorization response message (#0110).

Bit 55 Sub-elements in Authorization Response Messages (#0110)

Description Tag Length of Value Comments

Issuer Authentication Data 91 Variable (...16) Conditional

Issuer Script Template 1 71 Variable (...128) Conditional

Issuer Script Template 2 72 Variable (...128) Conditional

 NOTE: The hexadecimal representation of the Tag is given above.

Every two positions of hexadecimal data equal one byte of binary data.
*: This is related to EMV transaction. Licensees must receive the prior approval of JCBI if they plan to handle IC
card transactions.
**: The sum of the length of ‘Issuer Script Template 1’ and ‘Issuer Script Template 2’ must not exceed 128
bytes. Furthermore, in case that the JCB IC Card credit application that is compliant to the CCD Specification is
used, an Issuer shall send no more than one Issuer Script Template in the authorization response message.

Bit 56 Reserved ISO

Length 1 binary byte, then up to 999 characters

Format LLVAR binary, numeric and character (can be a binary data) string

Description Not supported

Bits 57-59 Reserved national

Length 1 binary byte, then up to 999 characters

Format LLVAR binary, numeric and character (can be a binary data) string

Description Not supported

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 60 STIP Related Information

Length 1 binary byte, then up to 255 characters

Format LLVAR binary, numeric and character (can be binary data) string

Description

Contains information for Stand-In processing.

The total Bit60 length is specified in its first byte, followed by each sub-element that begins with a two-byte tag
and an associated two-byte length indicator. The sub-elements within bit 60 need not be in any particular
order or sequence.

Bit 60 Data Layout

Total length of this 1st sub-field 2nd sub-field …. Nth sub-field

field (Bit60) Tag Length Value Tag Length Value Tag Length Value

Bit 60 Sub-elements

Description Tag Length Valid value Message Condition

STIP Institution 01 1 0: Unknown 0120 Stand-in

1: JCBI 0121
2: Acquirer

STIP Reason 02 1 0: Unknown 0120 Stand-in

1: Issuer Limit 0121
2: Special Cardmember Limit
3: System/Network Down
4: Time out occurred

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Description Tag Length Valid value Message Condition

STIP Rejected 03 2 00: Unknown* 0120 Stand-in

Reason 01: AC Verification Error 0121 performed &
02: TVR/CVR Check Error response
03: Listed on Cardnumber Negative code is not
File “Approve”
04:Listed on Merchant Negative File
05:Check Digit Error
06: PIN Verification Error
07: Expiration Date Error
08: Service Code Error
09: Invalid Cardnumber Range
10: CAV Verification Error
11: Over Special Cardmember Limit
(Amount)
12: Over Special Cardmember Limit
(Count)
13: Over Activity Limit (Amount)
14: Over Activity Limit (Count)
15: CAVV Verification Error
*: Set if an applicable value is not listed above when the Acquirer performs Stand-in.

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 61 Point of Service Information

Length 1 binary byte, then up to 255 characters

Format LLVAR binary, numeric and character (can be binary data) string

Description Consists of two sub-fields: one-byte length (currently set at ‘06’; length may be extended in
future), and POS Information.
Position 1: Mail/Telephone Order Transaction Sign
0:Unknown
1:Mail/Telephone Order Transaction
2:Non-Mail/Telephone Order Transaction
Position 2: Recurring Transaction Sign
0:Unknown
1:Recurring Transaction
2:Nonrecurring Transaction
Position 3: Pre-Authorization Sign
0:Unknown
1:Pre-Authorization
2:No Pre-Authorization
Positions 4,5 and 6: Terminal Located Country Code
Indicates the country where the terminal is located (not the acquirer) using the numeric
Country Codes defined in Code List.
If country is unknown/unspecified, indicate value as 900.

 NOTE : Pre-authorization is only allowed for hotel and rent-a-car Merchants.

Bit 62 Reserved private

Length 1 binary byte, then up to 999 characters

Format LLVAR binary, numeric and character (can be a binary data) string

Description Not supported

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 63 Transaction code

Length 1 binary byte, then up to 255 characters

Format LLVAR binary, character string

Format Numeric 4-bit BCD

Description Not supported

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 70 Network management information code

Length 3 digits, 2 bytes

Format Numeric 4-bit BCD (unsigned, packed)

This field indicates the required network management function carried by a network
Description
management request (0800) message. The management functions are as follows:

X'0001' Sign-on

5. Original forwarding institution identification code n 11 (bit map 33)

Bit 91 File update code

Length 1 digit, 1 byte

Format Alphabetic and numeric characters (EBCDIC)

Description Not supported

Bit 92 File security code

Length 2 digits, 2 bytes

Format Alphabetic and numeric characters (EBCDIC)

Description Not supported

Bit 93 File security code

Length 5 digits, 5 bytes

Format Alphabetic and numeric characters (EBCDIC)

Description Not supported

Bit 94 Service indicator

Length 7 digits, 7 bytes

Format Alphabetic and numeric characters (EBCDIC)

Description Not supported

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 95 Replacement amounts

Length 42 digits, 42 bytes

Format Alphabetic and numeric characters (EBCDIC)

Description This field should be used for partial reversals.

Subfield 1 / Positions 1-12 - Actual Amount, Transaction

Indicates the actual transaction amount.

*If bit 28 (Amount, transaction fee) is present, this amount includes ATM Access Fee in
the currency of bit 4 (Amount transaction)..
*If the reversal is a partial reversal, the value for this field must be less than the amount in
bit 4 (Amount, transaction).

Subfield 2 / Positions 13-24 - Zero Fill

Indicates zeros

Subfield 3 / Positions 25-36 - Actual Amount, Cardholder Billing

Indicates the actual amount in the issuer currency.
The value of this subfield is zero between an Acquirer and JCB.

Subfield 4 / Positions 37-42 - Zero Fill

Indicates zeros

Bit 96 Message security code for Single DES

Length 64 bits, 8 bytes

Format Numeric bit string

Description If bit 70 is X'0101', a new key for encryption should be placed in this field.
This field contains encrypted KPE by KEK for Single DES.

Bit 97 Amount, net settlement

Length 1 character indicating debit ('D') or credit ('C'), then 16 numeric digits (total of 9 bytes)

Format 1 character and numeric 4-bit BCD (unsigned, packed)

Description Not supported

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 98 Payee
Length 25 digits, 25 bytes

Format Alphabetic, numeric, and special characters (EBCDIC)

Description Not supported

Bit 99 Settlement institution identification code

Length 1 binary byte, then up to 11 digits (maximum of 7 bytes)

Format LLVAR binary, numeric 4-bit BCD (unsigned, packed)

Description Not supported

Bit 100 Receiving institution identification code

Length 1 binary byte, then up to 11 digits (maximum of 7 bytes)

Format LLVAR binary, numeric 4-bit BCD (unsigned, packed)

Description 0800
Contains the code of the final destination of the request message, i.e., the default
authorizing institution. Values must be defined under bilateral agreement in accordance
with the J-Link certification procedures.

0302
Contains institution identification code who should receive this record registration/inquiry
request. When used, this field must be set to 08’88070000’.

Bit 101 File name

Length 1 binary byte, then up to 17 digits, 17 bytes

Format LLVAR binary; alphabetic, numeric, and special characters (EBCDIC)

Description Set 04’6332’.

Bit 102 Account identification 1

Length 1 binary byte, then up to 28 digits, 28 bytes

Format LLVAR; alphabetic, numeric, and special characters (EBCDIC)

Description Not supported

Bit 103 Account identification 2

Length 1 binary byte, then up to 28 digits, 28 bytes

Format LLVAR binary; alphabetic, numeric, and special characters (EBCDIC)

Description Not supported

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 120 Record data

Length 2 binary bytes then up to 30 digits

Format LLLVAR binary (2 bytes : 0000 – FFFF); alphabetic, numeric, and special characters
(EBCDIC)

Description

Contains the record for a record registration/inquiry request.

There are three formats for Bit 120 of 0302/0312 messages as shown in the chart below. The format to be
used depends on the transaction type specified in sub-field 1 (transaction type) and whether the card number is
requested to be included in any regional version of the Stop List. The length of Bit 120 varies by the format and
is defined in the first two bytes of Bit 120.
The Cardnumber added on the Stop File must be included on the Negative File with “Pick-up” status.

Sub-field Sub-field Name Bytes Valid Values Format 1 Format 2 Format 3

No. (Attr)

0 Length of Variable Field 2 001E: Format 1 M M M

that Follows 0019: Format 2
0011: Format 3

1 Transaction Type 1 0 : Delete M M M

(EBCDIC) 1 : Add
2 : Revise
5 : Inquiry

2 JCB Card Number 16 PAN M M M

(EBCDIC)

3 Authorization Action Code 2 01: Refer to Issuer M M /

(EBCDIC) 04: Pick Up
05: Decline
07: Pick up Fraud
41: Pick up Lost
43: Pick Up Stolen

4 Purge Date 6 YYYYMM M M /

(EBCDIC)

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

5 Stop Region Sign 1 0 : Do not include in Stop M / /

Japan (EBCDIC) List for the region

6 Asia 1 1 : Include in Stop List for M / /

(EBCDIC) the region

7 USA 1 M / /
(EBCDIC)

8 Europe 1 M / /
(EBCDIC)

9 Local 1 M / /
(EBCDIC)

Transaction Type 1 (Add)

Formats 1 and 2 of 0302/0312 can be used for Transaction Type 1 (Add). When a card number needs to be
included in a Stop List and registered in the Negative File, Format 1 is to be used. When a card number needs
to be registered in the Negative File but does not need to be included in a Stop List, the request can be in either
Format 1 or Format 2.

The format used in the reply message must be the same as that used in the request message.

Sub-field No. Sub-field Name 302 Format 302 Format 312 Format 312 Format
1 2 1 2

0 Length M M M M

1 Transaction Type M M ME ME

2 JCB Card Number M M ME ME

3 Authorization Action Code M M ME ME

4 Purge Date M M ME ME

5 Stop Region Sign M / ME /

Japan

6 Asia M / ME /

7 USA M / ME /

8 Europe M / ME /

9 Local M / ME /

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Transaction Type 2 (Revise)

Formats 1 and 2 of 0302 and 0312 are applicable for Transaction Type 2 (Revise). When the revision
concerns the Stop List related information, Format 1 needs to be used. When the revision concerns only the
Action Code and/or the Purge Date, the request can be in either Format 1 or Format 2. The format used in
the reply message must be the same as that used in the request message.

Sub field No. Sub Field Name 302 Format 302 Format 312 Format 312 Format
1 2 1 2

0 Length M M M M

1 Transaction Type M M ME ME

2 JCB Card Number M M ME ME

3 Authorization Action Code M M ME ME

4 Purge Date M M ME ME

5 Stop Region Sign M / ME /

Japan

6 Asia M / ME /

7 USA M / ME /

8 Europe M / ME /

9 Local M / ME /

Transaction Type 0 (Delete)

For deletion requests, any format of Format 1, 2 or 3 can be used. The format used in the reply message
must be the same as that used in the request message.

Sub Sub Field Name 302 302 302 312 312 312
field Format 1 Format 2 Format 3 Format 1 Format 2 Format 3
No.

0 Length M M M M M M

1 Transaction Type M M M ME ME ME

2 JCB Card Number M M M ME ME ME

3 Authorization Action M M / ME ME /
Code

4 Purge Date M M / ME ME /

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

5 Stop Region Sign M / / ME / /

Japan

6 Asia M / / ME / /

7 USA M / / ME / /

8 Europe M / / ME / /

9 Local M / / ME / /

Transaction Type 5 (Inquiry)

For inquiry requests, only Format 3 is valid for a 0302 request message. The reply is always in Format 1.

Sub field Sub Field Name 302 Format 3 312 Format 1

No.

0 Length M M

1 Transaction Type M ME

2 JCB Card Number M ME

3 Authorization Action Code / M

4 Purge Date / M

5 Stop Region Sign / M

Japan

6 Asia / M

7 USA / M

8 Europe / M

9 Local / M

Bits 121-126 Reserved for private use

Length 1 binary byte, then up to 999 digits, 999 bytes

Format LLVAR binary; alphabetic, numeric, and special characters (EBCDIC)

Description Not supported

Bit 127 Negative data access code

Length 2 binary bytes, then up to 6 digits

Format LLLVAR binary (2 bytes : 0000 – FFFF); alphabetic, numeric, and special characters
(EBCDIC)

Description Contains negative data access code assigned to each Issuer by JCBI.

JCB Regulatory Publications

System Specifications – Online Interface Guide
Chapter 5 Message Format

Bit 128 Message authentication code

Length 64 bits

Format Bit string

Description Not supported

EMV Implementation Tandem Supplemental Guide
100% (2)
EMV Implementation Tandem Supplemental Guide
355 pages
Technical - Specifications-PayPass - PDS v1.9 (June 2014)
100% (2)
Technical - Specifications-PayPass - PDS v1.9 (June 2014)
107 pages
J-Secure 2.0 Acquirer Implementation Guide - v1.2
No ratings yet
J-Secure 2.0 Acquirer Implementation Guide - v1.2
32 pages
ARP Tables Lookup Algorithms
No ratings yet
ARP Tables Lookup Algorithms
3 pages
Book 4
No ratings yet
Book 4
33 pages
EMV CPS v1.1
67% (3)
EMV CPS v1.1
104 pages
EMV v4.3 Book1 ICC To Terminal Interface 2011113003541414
100% (1)
EMV v4.3 Book1 ICC To Terminal Interface 2011113003541414
189 pages
Postilion Developer External
No ratings yet
Postilion Developer External
2 pages
HSM and Thales Basics Using The Thales Simulator PDF
100% (1)
HSM and Thales Basics Using The Thales Simulator PDF
15 pages
ProCash NDC V2000 ProConsult NDC V2000 UserGuide en
No ratings yet
ProCash NDC V2000 ProConsult NDC V2000 UserGuide en
420 pages
CSR System Monitor Administrator/ Configurator Developer: Virtual Instructor-Led Training Instructor-Led Training
100% (2)
CSR System Monitor Administrator/ Configurator Developer: Virtual Instructor-Led Training Instructor-Led Training
1 page
Visa EMV 3DS Compliant Vendor Product List - 22jan2020
No ratings yet
Visa EMV 3DS Compliant Vendor Product List - 22jan2020
3 pages
Computer Sales and Service Management System
No ratings yet
Computer Sales and Service Management System
8 pages
Sg245204 - Subarea To APPN Migration - HPR and DLUR Implementation
No ratings yet
Sg245204 - Subarea To APPN Migration - HPR and DLUR Implementation
356 pages
TRUMPF System Requirements 2-26
No ratings yet
TRUMPF System Requirements 2-26
27 pages
Fis 8583-2017
No ratings yet
Fis 8583-2017
600 pages
Sarvatra Switch Iso8583 Message Samples
No ratings yet
Sarvatra Switch Iso8583 Message Samples
27 pages
DDC V3100 ExtensionGuide en
No ratings yet
DDC V3100 ExtensionGuide en
26 pages
CR - SingleMessageSystemSpecifications - Abril 2024
No ratings yet
CR - SingleMessageSystemSpecifications - Abril 2024
1,028 pages
MC - Member ICC Testing Procedures
100% (1)
MC - Member ICC Testing Procedures
161 pages
PayPass - MChip - Acquirer - Imlementation - Requirements - PPMCAIR (V1.0 - July 2008)
No ratings yet
PayPass - MChip - Acquirer - Imlementation - Requirements - PPMCAIR (V1.0 - July 2008)
88 pages
ISO Global 2008 3
100% (1)
ISO Global 2008 3
294 pages
H2Hspecs PDF
No ratings yet
H2Hspecs PDF
174 pages
Zimswitch Technical Spec Including3PA v0-51
No ratings yet
Zimswitch Technical Spec Including3PA v0-51
56 pages
Quick Chip For EMV and QVSDC, Specification Version 2.0 (Visa, 2017)
No ratings yet
Quick Chip For EMV and QVSDC, Specification Version 2.0 (Visa, 2017)
18 pages
BAEMSG Base24 Prosa
100% (1)
BAEMSG Base24 Prosa
602 pages
Refreshment Training On All Digital Products and Services
No ratings yet
Refreshment Training On All Digital Products and Services
132 pages
3DS 2.2 FAQs - v1.0 JULY 2019 FINAL
No ratings yet
3DS 2.2 FAQs - v1.0 JULY 2019 FINAL
4 pages
Wincor Nixdorf NDC - Extension For EMV
No ratings yet
Wincor Nixdorf NDC - Extension For EMV
58 pages
Jpos
100% (1)
Jpos
53 pages
BASE24 DR With AutoTMF and RDF Whitepaper
No ratings yet
BASE24 DR With AutoTMF and RDF Whitepaper
38 pages
Users Manual 3704697
No ratings yet
Users Manual 3704697
442 pages
UPI QuickPass Testing Guide For Acquirers - V201905
100% (1)
UPI QuickPass Testing Guide For Acquirers - V201905
14 pages
TechTrex Company & SecurePro Introduction V16
No ratings yet
TechTrex Company & SecurePro Introduction V16
27 pages
ATMIA - Next-Gen ATM Blueprint v1.5 Public Draft, Jun-2019
No ratings yet
ATMIA - Next-Gen ATM Blueprint v1.5 Public Draft, Jun-2019
1 page
PayPass - MChip (V1.3)
No ratings yet
PayPass - MChip (V1.3)
125 pages
Custom PPF
No ratings yet
Custom PPF
28 pages
Tag Definition EMV
100% (1)
Tag Definition EMV
2 pages
Terminal Information To Enhance Contactless Application Selection
No ratings yet
Terminal Information To Enhance Contactless Application Selection
10 pages
A Guide To EMV Chip Technology v3.0 1
No ratings yet
A Guide To EMV Chip Technology v3.0 1
33 pages
Pin Block Formats: David Tushie
No ratings yet
Pin Block Formats: David Tushie
3 pages
Vip System Sms Atm Processing Specs Intl
No ratings yet
Vip System Sms Atm Processing Specs Intl
210 pages
Visa Merchant Data Standards Manual
No ratings yet
Visa Merchant Data Standards Manual
249 pages
M/Chip Functional Architecture For Debit and Credit: Applies To: Summary
No ratings yet
M/Chip Functional Architecture For Debit and Credit: Applies To: Summary
12 pages
csfb400 Icsf Apg hcr77d1 PDF
No ratings yet
csfb400 Icsf Apg hcr77d1 PDF
1,720 pages
DCI Contactless D-PAS Acquirer Host Test Plan v1.2
No ratings yet
DCI Contactless D-PAS Acquirer Host Test Plan v1.2
88 pages
NDC Emv 300pdf
No ratings yet
NDC Emv 300pdf
560 pages
HSM I&O Manual 1270A513-3 PDF
No ratings yet
HSM I&O Manual 1270A513-3 PDF
202 pages
Racal Eracom Mapping
No ratings yet
Racal Eracom Mapping
2 pages
Mpos Development Guidelines
100% (1)
Mpos Development Guidelines
10 pages
Public Key Infrastructure - Certification Authority Interface
No ratings yet
Public Key Infrastructure - Certification Authority Interface
44 pages
BUI Smartvista Cbs Specification
No ratings yet
BUI Smartvista Cbs Specification
62 pages
EMVCo 3DS SDKSpec 220 122018
No ratings yet
EMVCo 3DS SDKSpec 220 122018
130 pages
Dynamic Currency Conversion Explained ? 1666789070
No ratings yet
Dynamic Currency Conversion Explained ? 1666789070
1 page
VTS Learninginz
No ratings yet
VTS Learninginz
6 pages
FileTransferMethods MasterCard
100% (2)
FileTransferMethods MasterCard
6 pages
CONTACTLESS v1.2
No ratings yet
CONTACTLESS v1.2
16 pages
CRM9250N Toolplus-Cassette-Config User Manual V1.1
No ratings yet
CRM9250N Toolplus-Cassette-Config User Manual V1.1
52 pages
EFT Switch: Next-Generation Multi-Channel EFT Switch For Processing Digital Payment Transactions
No ratings yet
EFT Switch: Next-Generation Multi-Channel EFT Switch For Processing Digital Payment Transactions
4 pages
POS DynmCurrConv
No ratings yet
POS DynmCurrConv
58 pages
PBT 01 EFT Overview
100% (2)
PBT 01 EFT Overview
72 pages
Emv Especifications
No ratings yet
Emv Especifications
44 pages
Content Creation Revolution with chatGPT
From Everand
Content Creation Revolution with chatGPT
Maria Cowen
No ratings yet
BASE24 R6.0 Post v10 2017-03-17 - BIC ISO Standards Manual
No ratings yet
BASE24 R6.0 Post v10 2017-03-17 - BIC ISO Standards Manual
308 pages
1983 National 74HC Databook
No ratings yet
1983 National 74HC Databook
608 pages
Guide Bios HP 8300 SFF
No ratings yet
Guide Bios HP 8300 SFF
15 pages
ESP32 Tutorial What Do You Have To Know About The ESP32 Microcontroller
No ratings yet
ESP32 Tutorial What Do You Have To Know About The ESP32 Microcontroller
10 pages
Topcon FC 500
No ratings yet
Topcon FC 500
4 pages
A6V11852727 - Desigo CC Compact DMS (Global) - en
No ratings yet
A6V11852727 - Desigo CC Compact DMS (Global) - en
6 pages
Bouncing Balls
No ratings yet
Bouncing Balls
6 pages
0 - COSC 223 Course Outline
No ratings yet
0 - COSC 223 Course Outline
2 pages
AC500 System
No ratings yet
AC500 System
18 pages
Object Oriented Programming Concept by Using C++ (CSEN 3208)
No ratings yet
Object Oriented Programming Concept by Using C++ (CSEN 3208)
3 pages
TIB Ebx 6.1.3 Container Edition
No ratings yet
TIB Ebx 6.1.3 Container Edition
24 pages
IPC - ST
No ratings yet
IPC - ST
95 pages
Uface 800: Dual Mode Biometric Time and Attendance Terminal
No ratings yet
Uface 800: Dual Mode Biometric Time and Attendance Terminal
2 pages
Fundamentals of Object Oriented Programming
No ratings yet
Fundamentals of Object Oriented Programming
26 pages
BR e-STUDIO2822AF 2822AM 201908
No ratings yet
BR e-STUDIO2822AF 2822AM 201908
4 pages
Csproject Amusementpark
No ratings yet
Csproject Amusementpark
49 pages
UD22560B A - Network Stable Positioning System - User Manual - H5, 5.5.45 - 20211119
No ratings yet
UD22560B A - Network Stable Positioning System - User Manual - H5, 5.5.45 - 20211119
106 pages
D2Loader-1 12
No ratings yet
D2Loader-1 12
4 pages
Hotel Management System
No ratings yet
Hotel Management System
82 pages
SAP Ui5 Fiori OData CDS Course Content-1
No ratings yet
SAP Ui5 Fiori OData CDS Course Content-1
11 pages
Weblogic Administration in Linux&Solaris
No ratings yet
Weblogic Administration in Linux&Solaris
3 pages
UNIT-3, Programming in C NOTES
No ratings yet
UNIT-3, Programming in C NOTES
58 pages
Indiviual Assignment: Smart Home Control System
No ratings yet
Indiviual Assignment: Smart Home Control System
23 pages
The history of windows
No ratings yet
The history of windows
3 pages
ePO 4.5 and 4.6 Server Backup and Disaster Recovery Procedure
No ratings yet
ePO 4.5 and 4.6 Server Backup and Disaster Recovery Procedure
8 pages
Vodafone Mobile Broadband - 11 2 0 52566 RC1 - ReadMe PDF
100% (1)
Vodafone Mobile Broadband - 11 2 0 52566 RC1 - ReadMe PDF
17 pages
Pre-Implementation Steps: Only Valid For The Following Sap - Basis Releases/Sps
No ratings yet
Pre-Implementation Steps: Only Valid For The Following Sap - Basis Releases/Sps
7 pages