JR/T 0055.3-2009 PDF in English
JR/T 0055.3-2009 (JR/T0055.3-2009, JRT 0055.3-2009, JRT0055.3-2009)
Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Name of Chinese Standard | Status |
JR/T 0055.3-2009 | English | 150 |
Add to Cart
|
0-9 seconds. Auto-delivery.
|
Technical specifications on bankcard interoperability. Part 3: File data format
| Valid |
Standards related to (historical): JR/T 0055.3-2009
PDF Preview
JR/T 0055.3-2009: PDF in English (JRT 0055.3-2009) JR/T 0055.3-2009
JR
FINANCIAL INDUSTRY STANDARD OF
THE PEOPLE’S REPUBLIC OF CHINA
ICS
File No..
Technical specifications on bankcard interoperability
- Part 3. File data format
ISSUED ON. JUNE 1, 2009
IMPLEMENTED ON. JULY 1, 2009
Issued by. People's Bank of China
3. No action is required - Full-copy of this standard will be automatically &
immediately delivered to your EMAIL address in 0~60 minutes.
Table of Contents
Foreword ... 3
1 Scope .. 4
2 Normative references ... 4
3 Symbols.. 4
4 File name ... 5
5 File description .. 5
6 Ordinary financial transaction details file ... 6
7 Transfer transaction details file ... 8
8 Adjustment details file ... 9
9 Summary file ... 11
Bibliography ... 13
Foreword
JR/T 0055 Technical specifications on bankcard interoperability consists of the
following five parts.
- Part 1. Transaction processing;
- Part 2. Message interface;
- Part 3. File data format;
- Part 4. Data secure transmission control;
- Part 5. Communication interface.
This Part is Part 3 of JR/T 0055.
This Part was proposed by People's Bank of China.
This Part shall be under the jurisdiction of National Technical Committee on
Finance of Standardization Administration of China.
Main drafting organizations of this Part. People's Bank of China Science and
Technology Division, China UnionPay Co., Ltd.
The drafting organizations of this Part. Industrial and Commercial Bank of China,
Agricultural Bank of China, Bank of China, China Construction Bank, HSBC
Bank, China Financial Computerization Corporation, Bank Card Testing Center.
Main drafters of this Part. Jiang Yunbing, Du Ning, Huang Faguo, Li Jie, Wan
Gaofeng, Lu Erdong, Shi Dapeng, Lin Song, Zeng Zheng, Deng Lifeng, Cao
Ying, Ma Xiaoqiong, Liu Zhigang.
Technical specifications on bankcard interoperability
- Part 3. File data format
1 Scope
This Part of this Standard specifies the file data format passed and exchanged
between agency and switching center, including file naming and record format
definition. This Part does not specify the file transmission method. The specific
transmission method shall be confirmed by all parties involved in the transaction.
This Part of this Standard applies to the switching center, the acquirer, the
issuer who conduct the inter-bank transaction of bank card.
2 Normative references
The provisions in following documents become the provisions of this Standard
through reference in this Standard. For dated references, the subsequent
amendments (excluding corrigendum) or revisions do not apply to this Standard,
however, parties who reach an agreement based on this Standard are
encouraged to study if the latest versions of these documents are applicable.
For undated references, the latest edition of the referenced document applies.
GB/T 15150-94, Bank card originated messages - Interchange message
specifications - Content for financial transactions (ISO 8583.1987)
3 Symbols
The symbols in this Part are described in Table 1.
Table 1 -- Symbolic notation
Symbol Instruction
a Letter a ~ z
n Number 0 ~ 9
s Special character
an Letter and numeric character
as Letter and special character
ns Number and special character
ans Letter, number and special character
MM Month, 01 to 12
Date of settlement See description on field 15 in Part 2 Message interface specifications n4
Message type Message type corresponding to online request message (not reply message) n4
Transaction treatment code See description on field 3 in Part 2 Message interface specifications n6
Merchant type See description on field 18 in Part 2 Message interface specifications n4
Enter method code of
service point
See description on field 22 in Part 2 Message
interface specifications n3
Function code See description on field 25 in Part 2 Message interface specifications n2
Retrieve reference number See description on field 37 in Part 2 Message interface specifications an12
Authorization identification
reply code
See description on field 38 in Part 2 Message
interface specifications an6
Reply code See description on field 39 in Part 2 Message interface specifications an2
Terminal identification code
of card accepter
See description on field 41 in Part 2 Message
interface specifications ans8
Card accepter identification
code
See description on field 42 in Part 2 Message
interface specifications ans15
Transaction currency code See description on field 49 in Part 2 Message interface specifications an3
Settlement currency code
See description on field 50 in Part 2 Message
interface specifications, appearing in the document
with exchange rate information
an3
Settlement exchange rate
See description on field 9 in Part 2 Message interface
specifications, appearing in the document with
exchange rate information
n8
Transaction initiation
channel
See description on “transaction initiation channel” in
field 60 in Part 2 Message interface specifications n2
Original transaction system
tracking number
See description on field 90.2 in Part 2 Message
interface specifications n6
Original transaction date and
time
See description on field 90.3 in Part 2 Message
interface specifications n10
Receiving agency
identification code
See description on field 100 in Part 2 Message
interface specifications n11
Agency receivable fee Calculated by switching center n12
Agency payable fee Calculated by switching center n12
Card serial number See description on field 23 in Part 2 Message interface specifications n3
8.2 Record format
This Standard only provides the transaction information that shall be at least
included in the adjustment records, as shown in Table 7. All parties involved in
the transaction shall add other supplementary information based on actual
needs.
Table 7 -- Record formats of adjustment details
Field name Editable value Type length
Adjustment identification
This identification distinguishes each type of
adjustment. The value shall be agreed by all the
parties involved in the transaction.
an3
Identification code of
acquiring agency
See description on field 32 in Part 2 Message
interface specifications n11
Identification code of issuing
agency
See description on field 33 in Part 2 Message
interface specifications n11
System tracking number See description on field 11 in Part 2 Message interface specifications n6
Transaction transfer time See description on field 7 in Part 2 Message interface specifications n10
Main account See description on field 2 in Part 2 Message interface specifications n19
Amount of transaction See description on field 2 in Part 2 Message interface specifications n12
Amount of settlement
See description on field 5 in Part 2 Message interface
specifications, appearing in the adjustment details file
with exchange rate information
n12
Merchant type See description on field 18 in Part 2 Message interface specifications n4
Enter method code of
service point
See description on field 22 in Part 2 Message
interface specifications n3
Function code See description on field 25 in Part 2 Message interface specifications n2
Retrieve reference number See description on field 37 in Part 2 Message interface specifications an12
Authorization identification
reply code
See description on field 38 in Part 2 Message
interface specifications an6
Reply code See description on field 39 in Part 2 Message interface specifications an2
Terminal identification code
of card accepter
See description on field 41 in Part 2 Message
interface specifications ans8
Identification code of card
accepter
See description on field 42 in Part 2 Message
interface specifications ans15
Transaction currency code See description on field 49 in Part 2 Message interface specifications an3
...... Source: Above contents are excerpted from the PDF -- translated/reviewed by: www.chinesestandard.net / Wayne Zheng et al.
|