J/SecureTM 2.

0 DS File Registration Procedures

Version 2.2.0
© JCB Co., Ltd. 2019 All rights reserved.

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

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

This documentation may contain any information regarding any third party’s information, patents,
copyrights, trademarks, trade secrets, know-how or other intellectual property rights, or any other rights.
JCB makes no representation, warranty or guarantee expressly nor impliedly regarding whether all or
any part of this documentation (written, graphics or otherwise) appearing whether in whole or in part,
regardless of form, does or does not violate, infringe or otherwise use the information, patents,
copyrights, trademarks, trade secrets, know-how or other intellectual property rights, or any other rights
of third parties. You shall be solely responsible for determining whether your activities require license or
permission from third parties. JCB shall not be liable for your or any third party’s infringement of any
intellectual property rights or any other rights of any third parties.

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

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

1.1. Purpose of this document ................................................................................................................ 1

1.2. Intended Readers .............................................................................................................................. 1

1.3. Revision of this document ............................................................................................................... 1

1.4. Related Documents ........................................................................................................................... 1

2. Issuer DS2.0 Registration Procedures ................................................................................................... 2

2.1. Issuer Requirement ........................................................................................................................... 2

2.1.1. Registration Flow ....................................................................................................................... 2

3. Acquirer DS2.0 Registration Procedures ............................................................................................... 3

3.1. Acquirer DS Registration and Update ............................................................................................. 3

3.2. User Account for Merchant Data Maintenance .............................................................................. 3

3.3. Registration Flow .............................................................................................................................. 3

4. DS2.0 File Creation ................................................................................................................................... 4

4.1. Issuer Related File............................................................................................................................. 4

4.2. Acquirer Related File ........................................................................................................................ 4

4.3. File Software ...................................................................................................................................... 4

4.4. Field Format ....................................................................................................................................... 4

4.5. File Name ........................................................................................................................................... 5

4.6. Submission Address ......................................................................................................................... 5

4.7. Submission Email title ...................................................................................................................... 5

4.8. Submission Schedule ....................................................................................................................... 5

5. DS2.0 Contact ID File (for Issuer) ........................................................................................................... 6

5.1. Sample File ........................................................................................................................................ 6

5.1.1. File Format .................................................................................................................................. 6

6. DS2.0 Card Range File (for Issuer) ......................................................................................................... 8

6.1. Sample File ........................................................................................................................................ 8

6.1.1. File Format .................................................................................................................................. 8

7. DS2.0 Acquirer BIN File (for Acquirer) ................................................................................................. 14

7.1. Sample File ...................................................................................................................................... 14

7.1.1. File Format ................................................................................................................................ 14

8. DS2.0 Acquirer Merchant File (for Acquirer)........................................................................................ 16

8.1. Sample File ...................................................................................................................................... 16

8.1.1. File Format ................................................................................................................................ 17

9. Contacts .................................................................................................................................................. 17
 J/Secure™2.0 DS File Registration Procedures

1. Introduction
This chapter describes the purpose, intended readers, scope, structure, revision policy and related
materials of this document.

1.1. Purpose of this document

In order to participate in J/Secure2.0, Issuers and Acquirers shall register cardmember and
merchant information on the J/Secure2.0 Directory Server (DS2.0). The purpose of this document is
to describe the necessary registration requirements and procedures.

1.2. Intended Readers

This document is intended for Issuers, Acquirers or other Parties who register information on the
DS2.0.

1.3. Revision of this document

JCB may revise this document as necessary. Issuers and Acquirers shall follow the contents of
the revised version when it is distributed.

1.4. Related Documents

Related documents are as follows:
 J/Secure™2.0 Issuer Implementation Guide
 J/Secure™2.0 Acquirer Implementation Guide
 JCB Regulatory Publications
 J/Secure™2.0 Confidence Test Procedures
 J/Secure™2.0 Merchant Information Maintenance Guide

JCB Confidential 1 2018.10

 J/Secure™2.0 DS File Registration Procedures

2. Issuer DS2.0 Registration Procedures

This chapter describes procedures for Issuer Directory Server (DS2.0) registration.

2.1. Issuer Requirement

Issuers shall register and maintain information on the DS2.0 under their own responsibility. The
Issuer is responsible for correcting or deleting information registered on the DS2.0 when the
information changes or the user terminates use of J/Secure.

2.1.1. Registration Flow

Figure 1. Issuer DS Registration Flow

DS2.0 Contact ID File

DS2.0 Card Range File
1

Directory
Issuer JCBI
Internet 2 Server
(DS2.0)
3

1) The Issuer creates DS2.0 Contact ID File and DS2.0 Card Range File, and submits it
by e-mail to JCB
 Note: Each file shall be zipped and protected by a password, which is supplied by
JCB on the “Issuer Implementation Form for J/Secure2.0”.
2) JCB registers the Issuer’s information in the DS2.0 Contact ID File and DS2.0 Card
Range File onto the DS2.0.
3) JCB reports the result of DS2.0 registration to the Issuer.
JCB will inform the Issuer by e-mail if the file is registered successfully or if an error was
found. If an error was found, the Issuer needs to correct the file and re-submit it to JCB.
 Note: When revising the information in DS2.0, the Issuer creates only the file that
has changed. Please refer to Chapter 5 and 6 for more details.

JCB Confidential 2 2018.10

 J/Secure™2.0 DS File Registration Procedures

3. Acquirer DS2.0 Registration Procedures

This chapter describes the procedures for Acquirer and Merchant Directory Server (DS2.0)
registration.

3.1. Acquirer DS Registration and Update

Acquirers shall register and maintain information on the DS2.0 under their own responsibility. The
Acquirer is responsible for correcting or deleting information registered on the DS2.0 when the
information changes, the user terminates use of J/Secure2.0, or the Merchant Agreement is
terminated.

3.2. User Account for Merchant Data Maintenance

DS2.0 has Merchant Information Maintenance WEB for Acquirer. JCB will create the User
Account and inform it to the Acquirer after the Acquirer submits the DS2.0 Acquirer BIN File.

3.3. Registration Flow

Figure 2. Acquirer DS Registration Flow

DS2.0 Acquirer BIN

File via email
1
JCBI 2

Acquirer 3
Directory
Internet Server
(DS2.0)

Upload DS2.0 Merchant

File or input the merchant
data directly through
DS2.0 function

1) The Acquirer creates DS2.0 Acquirer BIN File and submits them by e-mail to JCB.
 Note: The file shall be zipped and protected by a password, which is supplied by JCB on the
“Acquirer Implementation Form for J/Secure2.0”.
2) JCB registers the Acquirer’s information in the DS2.0 Acquirer BIN File onto the DS2.0.
3) JCB reports the result of DS2.0 registration and User Account for Merchant Information
Maintenance WEB to the Acquirer.
JCB will inform the Acquirer by e-mail if the file is registered successfully or if an error was
found. If an error is found, the Acquirer needs to correct the file and re-submit it to JCB.
 Note: When revising the information in DS2.0, the Acquirer creates only the file that has
changed. Please refer to Chapter 3.2 for more information.
4) The Acquirer creates DS2.0 Acquirer Merchant File and uploads it through the uploading
function in DS2.0, or inputs the merchant data through the DS2.0 screen directly. DS2.0 will
inform the Acquirer if the uploaded data is registered successfully or if an error was found. If an
error is found, the acquirer need to correct the error records and re-upload only modified

JCB Confidential 3 2018.10

 J/Secure™2.0 DS File Registration Procedures

records.

4. DS2.0 File Creation

This chapter tells Issuers and Acquirers how to create Directory Server (DS2.0) files.

4.1. Issuer Related File

An Issuer shall submit the following DS2.0 file in order to register the Issuer’s information on the
DS2.0.
 DS2.0 Contact ID File
 DS2.0 Card Range File

4.2. Acquirer Related File

An Acquirer shall submit the following DS files in order to register the Acquirer’s information on the
DS2.0.
 DS2.0 Acquirer BIN File
 DS2.0 Acquirer Merchant File

4.3. File Software

DS2.0 files shall be created by a text editor such as Microsoft Notepad using the character code
“us-ascii”.

4.4. Field Format

Throughout the J/Secure2.0 DS File Registration Procedure, types of field format are defined as
follows:
Alphabet: English alphabet
Alphanumeric: English alphabet and numerals
Symbols: Special Characters

 English alphabet includes the following characters:

ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz

 Note: Alphabetic and alphanumeric formats are case sensitive.

 Symbols include the following characters:

Field Allowed Characters
Name !#$%&()=+*}<>?/.:;@-
Address !#$%&()=+*}<>?/.:;@-
E-mail @+-=_./!#$%*^`|'&{}
URL !#$%&()=+*?/.:;@-_'~
 Note: “, ” (comma), “ ‘ ” (single quotation), and “ “ ”(double quotation) are not allowed for
use in any field. “ ”(Space) is allowed only as noted in the file format descriptions.

JCB Confidential 4 2018.10

 J/Secure™2.0 DS File Registration Procedures

4.5. File Name

DS2.0 File names should be as follows:
(a) DS2.0 Contact ID File:
“YYYYMMDD(*)_int_contact_action(add or update)_ISS NAME_2.0”
ex)”20180401_int_contact_add_JCB_2.0”

(b) DS2.0 Card Range File:

“YYYYMMDD(*)_int_range_action(add, delete or update)_ISS NAME_2.0”
ex.) “20180401_int_range_add_JCB_2.0”

(c) DS2.0 Acquirer BIN File:

“YYYYMMDD(*)_int_acquirer_action(add, delete or update)_ACQ NAME_2.0”
ex.)”20180401_int_acquirer_add_JCB_2.0”

(d) DS2.0 Acquirer Merchant File:

“YYYYMMDD(*)_int_merchant_action(add, delete or update)_ACQ NAME_2.0”
ex.)”20180401_int_merchant_add_JCB_2.0”

(*) “YYYYMMDD” is the local date when you submit a DS2.0 file to JCB.

4.6. Submission Address

jsecure2.0-dsregistration@info.jcb.co.jp.

4.7. Submission Email title

J/Secure2.0 + File type(*) + ISS NAME/ACQ NAME
(*)The File type should be selected from “Contact ID File, Card Range File, or Acquirer BIN File.

4.8. Submission Schedule

JCB implements DS2.0 registration twice a week:
Cut-off date: every Sunday and Wednesday, the registration: every Monday and Thursday.
 Note: JCB will notify the ISS/ Acquirer if an error is found in the submitted file. The ISS/ Acquirer
needs to correct the file and re-submit it to JCB.

JCB Confidential 5 2018.10

 J/Secure™2.0 DS File Registration Procedures

5. DS2.0 Contact ID File (for Issuer)

Contact ID shall be registered before the Card Range.

5.1. Sample File

This is a sample DS2.0 Contact ID File.

Contact Name Address E-mail Phone Issuer Managed ID

Contact ID Contact Name Address E-mail Phone Issuer Managed ID

5.1.1. File Format

As shown in the sample in 5.1, the file consists of the 2 lines described as follows. Fields are
delimited with a comma. Any line feed codes are not allowed.

First Line

Acceptable
Field Inclusion Length Data Remarks
Character
Category Requirerd 7 Only Alphabet "contact" (constant)
"add" or "update" The "add" data shall come before
Action Requirerd 3 or 6 Only Alphabet
(constant) the "update"

JCB Confidential 6 2018.10

 J/Secure™2.0 DS File Registration Procedures

Second Line

Field Inclusion Length Field Type Data Remarks

Numeric The contact ID will be numbered

Contact Required for Up to
automatically when the action is
ID “update” 18
“add”.
Alphanumeric Spaces may be used for this field.
Contact Up to
Required Symbols Issuer Name Allowed symbols are
Name 250
“!#$%&()=+*}<>?/.:;@-“.
Alphanumeric Spaces may be used for this field.
Up to
Address Required Symbols Allowed symbols are
250
“!#$%&()=+*}<>?/.:;@-“
Up to Alphanumeric, Allowed symbols are
Email Required
250 symbols “@+-=_./!#$%*^`|'&{}”.
Up to Numeric
Phone Required
20
Issuer Numeric The Issuer Managed ID is assigned
Managed Required 10 to 20 by JCBI in Issuer Implementation
ID Form for J/Secure2.0.
 Note: “ ”(Space) is allowed only as noted in the file format descriptions.

JCB Confidential 7 2018.10

 J/Secure™2.0 DS File Registration Procedures

6. DS2.0 Card Range File (for Issuer)

Card Range File is available after registering Contact ID.

6.1. Sample File

This is a sample DS2.0 Card Range File.

16(constant) End of card range Start Protocol Version 3DS Method URL ACS1 End Protocol Version

Beginning of card range Contact ID ACS1 URL (you can set up 5 URLs) Base ACS Information Indicator (2.1.0)

End Protocol Version ACS1 Start Protocol Version ACS1 ACS Information Indicator (2.1.0)

Base ACS Information Indicator (2.2.0)

ACS1 ACS Information Indicator (2.2.0)

6.1.1. File Format

As shown in the sample in 6.1, the file consists of the 2 lines described as follows. Fields are
delimited with a comma. ACS related information (from ACS1 to 5) shall be set from the beginning.
Even if you do not set up ACS2, 3, 4, or 5, fill them with commas. Any line feed codes are not
allowed.

First Line

Acceptable
Field Inclusion Length Data Remarks
Character
Category Requirerd 5 Only Alphabet "range" (constant)
"add" or "update" or
Action Requirerd 3 or 6 Only Alphabet
"delete" (constant)

Second Line

Acceptable
Field Inclusion Length Data Remarks
Character

PAN Length Required 2 Numeric “16” (Constant)

JCB Confidential 8 2018.10

 J/Secure™2.0 DS File Registration Procedures

PAN Begin Required 16 Numeric

PAN End Required 16 Numeric

Contact ID Required Up to 18 Numeric

Indicates Protocol Version range.

Start Protocol Numeric The End Protocol Version shall
Required Up to 8 be the same or higher than Start
Version Symbol”.”
Protocol Version.
The Start Protocol Version shall
be the oldest value out of all ACS
End Protocol Numeric Start Protocol Version.
Required Up to 8 The End Protocol Version shall
Version Symbol”.”
be the newest value out of all
ACS End Protocol Version.
Shall start with “https://”.
3DS Method Alphanumeric
Optional Up to 256 Allowed symbols are
URL Symbol
“!#$%&()=+*?/.:;@-_'~”.
Shall start with “https://”.
Alphanumeric
ACS1 URL Required Up to 256 Allowed symbols are
Symbol
“!#$%&()=+*?/.:;@-_'~”.
ACS1 Start
Numeric Indicates ACS1 Protocol Version
Protocol Required Up to 8
Symbol”.” range.
Version
The End Protocol Version shall
ACS1 End
Numeric be the same or higher than Start
Protocol Required Up to 8
Symbol”.” Protocol Version.
Version
Shall start with “https://”.
Alphanumeric
ACS2 URL Optional Up to 256 Allowed symbols are
Symbol
“!#$%&()=+*?/.:;@-_'~”.
ACS2 Start Required when ACS2 URL is set
Numeric
Protocol Conditional Up to 8 up.
Symbol”.”
Version Indicates ACS2 Protocol Version
range.
ACS2 End
Numeric The End Protocol Version shall
Protocol Conditional Up to 8
Symbol”.” be the same or higher than Start
Version
Protocol Version.
Shall start with “https://”.
Alphanumeric
ACS3 URL Optional Up to 256 Allowed symbols are
Symbol
“!#$%&()=+*?/.:;@-_'~”.

JCB Confidential 9 2018.10

 J/Secure™2.0 DS File Registration Procedures

ACS3 Start Required when ACS3 URL is set

Numeric
Protocol Conditional Up to 8 up.
Symbol”.”
Version Indicates ACS3 Protocol Version
range.
ACS3 End
Numeric The End Protocol Version shall
Protocol Conditional Up to 8
Symbol”.” be the same or higher than Start
Version
Protocol Version.
Shall start with “https://”.
Alphanumeric
ACS4 URL Optional Up to 256 Allowed symbols are
Symbol
“!#$%&()=+*?/.:;@-_'~”.
ACS4 Start Required when ACS4 URL is set
Numeric
Protocol Conditional Up to 8 up.
Symbol”.”
Version Indicates ACS4 Protocol Version
range.
ACS4 End
Numeric The End Protocol Version shall
Protocol Conditional Up to 8
Symbol”.” be the same or higher than Start
Version
Protocol Version.
Shall start with “https://”.
Alphanumeric
ACS5 URL Optional Up to 256 Allowed symbols are
Symbol
“!#$%&()=+*?/.:;@-_'~”.
ACS5 Start Required when ACS5 URL is set
Numeric
Protocol Conditional Up to 8 up.
Symbol”.”
Version Indicates ACS5 Protocol Version
range.
ACS5 End
Numeric The End Protocol Version shall
Protocol Conditional Up to 8
Symbol”.” be the same or higher than Start
Version
Protocol Version.
Required when Protocol Version
contains “2.1.0”.
Allowed values are
Base ACS
01: Supports Authentication by
Information Numeric
Conditional Up to 299 ACS
Indicator Symbol”:”
02: Supports attempt by ACS or
(2.1.0)
DS
Separate multiple values by a colon
":".
Required when ACS1 Protocol
Version contains “2.1.0”.
Allowed values are
ACS1 ACS
01: Supports Authentication by
Information Numeric
Conditional Up to 299 ACS
Indicator Symbol”:”
02: Supports attempt by ACS or
(2.1.0)
DS
Separate multiple values by a colon
":".

JCB Confidential 10 2018.10

 J/Secure™2.0 DS File Registration Procedures

Required when ACS2 Protocol

Version contains “2.1.0”.
Allowed values are
ACS2 ACS
01: Supports Authentication by
Information Numeric
Conditional Up to 299 ACS
Indicator Symbol”:”
02: Supports attempt by ACS or
(2.1.0)
DS
Separate multiple values by a colon
":".
Required when ACS3 Protocol
Version contains “2.1.0”.
Allowed values are
ACS3 ACS
01: Supports Authentication by
Information Numeric
Conditional Up to 299 ACS
Indicator Symbol”:”
02: Supports attempt by ACS or
(2.1.0)
DS
Separate multiple values by a colon
":".
Required when ACS4 Protocol
Version contains “2.1.0”.
Allowed values are
ACS4 ACS
01: Supports Authentication by
Information Numeric
Conditional Up to 299 ACS
Indicator Symbol”:”
02: Supports attempt by ACS or
(2.1.0)
DS
Separate multiple values by a colon
":".
Required when ACS5 Protocol
Version contains “2.1.0”.
Allowed values are
ACS5 ACS
01: Supports Authentication by
Information Numeric
Conditional Up to 299 ACS
Indicator Symbol”:”
02: Supports attempt by ACS or
(2.1.0)
DS
Separate multiple values by a colon
":".
Required when Protocol Version
contains “2.2.0”.
Allowed values are
Base ACS 01: Supports Authentication by
Information Numeric ACS
Conditional Up to 299
Indicator Symbol”:” 02: Supports attempt by ACS or
(2.2.0) DS
03: Supports Decoupled
Authentication
04: Supports Whitelisting

JCB Confidential 11 2018.10

 J/Secure™2.0 DS File Registration Procedures

Separate multiple values by a colon

":".

Required when ACS1 Protocol

Version contains “2.2.0”.
Allowed values are
01: Supports Authentication by
ACS1 ACS ACS
Information Numeric 02: Supports attempt by ACS or
Conditional Up to 299
Indicator Symbol”:” DS
(2.2.0) 03: Supports Decoupled
Authentication
04: Supports Whitelisting
Separate multiple values by a colon
":".
Required when ACS2 Protocol
Version contains “2.2.0”.
Allowed values are
01: Supports Authentication by
ACS2 ACS ACS
Information Numeric 02: Supports attempt by ACS or
Conditional Up to 299
Indicator Symbol”:” DS
(2.2.0) 03: Supports Decoupled
Authentication
04: Supports Whitelisting
Separate multiple values by a colon
":".
Required when ACS3 Protocol
Version contains “2.2.0”.
Allowed values are
01: Supports Authentication by
ACS3 ACS ACS
Information Numeric 02: Supports attempt by ACS or
Conditional Up to 299
Indicator Symbol”:” DS
(2.2.0) 03: Supports Decoupled
Authentication
04: Supports Whitelisting
Separate multiple values by a colon
":".
Required when ACS4 Protocol
Version contains “2.2.0”.
ACS4 ACS
Allowed values are
Information Numeric
Conditional Up to 299 01: Supports Authentication by
Indicator Symbol”:”
ACS
(2.2.0)
02: Supports attempt by ACS or
DS

JCB Confidential 12 2018.10

 J/Secure™2.0 DS File Registration Procedures

03: Supports Decoupled

Authentication
04: Supports Whitelisting
Separate multiple values by a colon
":".
Required when ACS5 Protocol
Version contains “2.2.0”.
Allowed values are
01: Supports Authentication by
ACS5 ACS ACS
Information Numeric 02: Supports attempt by ACS or
Conditional Up to 299
Indicator Symbol”:” DS
(2.2.0) 03: Supports Decoupled
Authentication
04: Supports Whitelisting
Separate multiple values by a colon
":".
 Note: “ ”(Space) is allowed only as noted in the file format descriptions.

JCB Confidential 13 2018.10

 J/Secure™2.0 DS File Registration Procedures

7. DS2.0 Acquirer BIN File (for Acquirer)

7.1. Sample File

This is a sample DS Acquirer BIN File.

ACQ BIN ACQ name Address E-mail Phone

ACQ BIN

7.1.1. File Format

As shown in the sample in 7.1, the file consists of the 2 lines described as follows. Fields are
delimited with a comma. Any line feed codes are not allowed.

First Line

Acceptable
Field Inclusion Length Data Remarks
Character
Category Required 8 Only Alphabet "acquirer" (constant)
"add" or "update" or
Action Required 3 or 6 Only Alphabet
"delete" (constant)

JCB Confidential 14 2018.10

 J/Secure™2.0 DS File Registration Procedures

Second Line

Acceptable
Field Inclusion Length Data Remarks
Character

Alphanumeric This field shall contain the Acquirer

ACQ BIN Required 8 Numeric BIN assigned by JCBI in Acquirer
Implementation Form for J/Secure2.0.
Alphanumeric Spaces may be used for this field.
ACQ Required for Up to
Symbols Allowed symbols are
Name add or update 250
“!#$%&()=+*}<>?/.:;@-“.
Alphanumeric Spaces may be used for this field.
Required for Up to
Address Symbols Allowed symbols are
add or update 250
“!#$%&()=+*}<>?/.:;@-“
Required for Up to Alphanumeric, Allowed symbols are
Email
add or update 250 symbols “@+-=_./!#$%*^`|'&{}”.
Required for Up to Numeric
Phone
add or update 20
 Note: “ ”(Space) is allowed only as noted in the file format descriptions.

JCB Confidential 15 2018.10

 J/Secure™2.0 DS File Registration Procedures

8. DS2.0 Acquirer Merchant File (for Acquirer)

This chapter explains only file format. Acquirers are required to upload it through Merchant
Information Maintenance WEB by one self. Regarding Merchant Information Maintenance WEB,
refer to its procedure.

8.1. Sample File

This is a sample DS2.0 Merchant file.

Merchant
Merchant ID Country Code
ACQ BIN Merchant Name Category Code

Merchant
Merchant ID Country Code
ACQ BIN Merchant Name Category Code

Merchant ID
ACQ BIN

 Note: 3DS Requestor ID will be added/updated/deleted automatically once the

Merchant ID is added/updated/deleted.

JCB Confidential 16 2018.10

 J/Secure™2.0 DS File Registration Procedures

8.1.1. File Format

As shown in the sample in 8.1, the file consists of the 2 lines described as follows. Fields are
delimited with a comma. Any line feed codes are not allowed.

First Line

Acceptable
Field Inclusion Length Data Remarks
Character
Category Required 8 Only Alphabet "merchant" (constant)
"add" or "update" or
Action Required 3 or 6 Only Alphabet
"delete" (constant)

Second Line

Acceptable
Field Inclusion Length Data Remarks
Character

Alphanumeric This field shall contain the Acquirer BIN

ACQ BIN Required 8 assigned by JCBI in Acquirer
Implementation Form for J/Secure2.0.
Acquirer Alphanumeric
Up to
Merchant Required
24
ID
Acquirer Required for Alphanumeric Spaces may be used for this field.
Up to
Merchant add or Hyphen may not be used.
40
Name update
Merchant Required for Numeric Refer to JCB Regulatory Publications'
Category add or 4 Code List
Code update
Merchant Required for Numeric Refer to JCB Regulatory Publications'
Country add or 3 Code List
Code update
 Note: “ ”(Space) is allowed only as noted in the file format descriptions.

9. Contacts

Name JCB International Co., Ltd.

E-mail Jsecure2.0-dsregistration@info.jcb.co.jp

JCB Confidential 17 2018.10

J/Secure2.0TM DS File Registration Procedures

Ver.2.2.0

Date of Issuance October 2019

Issuer: JCB Co. Ltd.
JCB International Co., Ltd.

Copyright © 2019 JCB CO.,LTD.

Unauthorized reproduction is strictly prohibited.