JR/T 0055.2-2009 English PDF (JR/T0055.2-2009)

Delivery: 2 working-hours manually (Sales@ChineseStandard.net)
Need delivered in 3-second? USA-Site: JR/T 0055.2-2009
Get Quotation: Click JR/T 0055.2-2009 (Self-service in 1-minute)
Historical versions (Master-website): JR/T 0055.2-2009
Preview True-PDF (Reload/Scroll-down if blank)

JR/T 0055.2-2009: Technical specifications on bankcard interoperability-Part 2: Message interface
JR/T 0055.2-2009
JR
FINANCIAL INDUSTRY STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS
Registration number
Technical specifications on bankcard interoperability -
Part 1. Message interface
ISSUED ON. JUNE 01, 2009
IMPLEMENTED ON. JULY 01, 2009
Issued by. People’s Bank of China
3. No action is required - Full-copy of this standard will be automatically and
immediately delivered to your EMAIL address in 0~60 minutes.
Table of Contents
Foreword ... 5 
1 Scope .. 6 
2 Normative references ... 6 
3 Terms and definitions ... 6 
4 Symbol ... 7 
4.1 Data type symbol ... 7 
4.2 Message format symbol ... 8 
4.3 Mandatory and conditional symbols of message fields ... 9 
5 Message structure ... 10 
6 Message header ... 11 
6.1 Field descriptions .. 11 
6.2 Message header of normal message ... 16 
6.3 Message header of reject message ... 16 
7 Message type .. 16 
7.1 Version number .. 16 
7.2 Message type flag ... 17 
8 Message bitmap ... 17 
9 Message field description ... 18 
9.1 Message field directory .. 18 
9.2 Field 2. Primary Account Number (PAN) ... 22 
9.3 Field 3. Processing code .. 23 
9.4 Field 4. Amount, Transaction ... 24 
9.5 Field 5. Amount, Settlement ... 24 
9.6 Field 6. Amount, Cardholder Billing ... 25 
9.7 Field 7. Transmission Date and Time ... 25 
9.8 Field 9. Conversion Rate, Settlement ... 26 
9.9 Field 10. Conversion Rate, Cardholder Billing ... 27 
9.10 Field 11. System Trace Audit Number ... 27 
9.11. Time, Local Transaction ... 28 
9.12 Field 13. Date, Local Transaction ... 29 
9.13 Field 14. Date, Expiration ... 29 
9.14 Field 15. Date, Settlement ... 30 
9.15 Field 16. Date, Conversion .. 30 
9.16 Field 18. Merchant's Type ... 31 
9.17 Field 19. Acquiring Institution Country Code .. 31 
9.18 Field 22. Point of Service Entry Mode Code .. 32 
9.19 Field 23. Card Sequence Number ... 32 
9.20 Field 25. Function Code .. 33 
9.21 Field 26. Point of Service PIN Capture Code ... 34 
9.22 Field 28. Amount, Transaction Fee .. 34 
9.23 Field 32. Acquiring institute identification code ... 35 
9.24 Field 33. Forwarding Institution Identification Code ... 35 
9.25 Field 35. Track 2 Data .. 36 
9.26 Field 36. Track 3 Data .. 37 
9.27 Field 37. Retrieval Reference Number ... 37 
9.28 Field 38. Authorization Identification Code ... 38 
9.29 Field 39. Response Code ... 38 
9.30 Field 41. Card Acceptor Terminal Identification ... 39 
9.31 Field 42. Card Acceptor Identification Code .. 40 
9.32 Field 43. Card Acceptor Name/Location .. 40 
9.33 Field 44. Additional Response Data ... 41 
9.34 Field 48. Additional Data Private ... 41 
9.35 Field 49. Currency Code, Transaction ... 42 
9.36 Field 50. Currency Code, Settlement .. 43 
9.37 Field 51. Currency Code, Cardholder Billing ... 43 
9.38 Field 52. Personal Identification Number (PIN) Data ... 44 
9.39 Field 53. Security Related Control Information ... 44 
9.40 Field 54. Additional Amounts .. 45 
9.41 Field 55. Integrated Circuit Card (ICC) System Related Data ... 46 
9.42 Field 57. Additional Data Private ... 49 
9.43 Field 58. IC (PBOC) Data Reserved ... 50 
9.44 Field 60. POS additional information .. 51 
9.45 Field 61. Cardholder Authentication Information .. 52 
9.46 Field 70. Network Management Information Code ... 54 
9.47 Field 90. Original Data Element ... 55 
9.48 Field 96. Message Security Code ... 55 
9.49 Field 100. Receiving Institution Identification Code ... 56 
9.50 Field 102. Account Identification 1 ... 56 
9.51 Field 103. Account Identification 2 ... 57 
9.52 Field 121. Switch Reserved ... 57 
9.53 Field 122. Acquiring Institution Reserved ... 58 
9.54 Field 123. Issuer Institution Reserved ... 58 
9.55 Field 128. Message Authentication Code ... 59 
10 Correlation of key information field to message ... 60 
10.1 Correlation of response message and request message .. 60 
10.2 Correlation of subsequent transactions and original transactions ... 60 
11 Message format description ... 61 
11.1 Financial transaction online message ... 61 
11.2 Management transaction online message .. 81 
Appendix A (Normative) Reject code ... 84 
Appendix B (Normative) Transaction type code .. 88 
Appendix C (Normative) Response code ... 90 
Appendix D (Informative) Transaction type distinction table ... 93 
References ... 95 
Foreword
JR/T 0055 “Technical specifications on bankcard interoperability” consists of the
following 5 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 2 of JR/T 0055.
Appendix A, Appendix B and Appendix C of this part are normative; Appendix
D is informative.
This part was proposed by the People's Bank of China.
This part shall be under the jurisdiction of the National Financial Standardization
Technical Committee.
The responsible drafting organizations of this part. People's Bank of China
Science and Technology Division, China UnionPay Co., Ltd.
The participating drafting organizations of this part. Industrial and Commercial
Bank of China, Agricultural Bank of China, Bank of China, China Construction
Bank, Huaxia Bank, China Financial Electronics Co., Ltd., Bank Card Testing
Center.
The 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 2. Message interface
1 Scope
This standard specifies the message interface for online transactions between
the institution and the switching center, including the structure, format, and
message field of the online transaction message.
This part of this standard applies to all the institutions such as the switching
center, acquirer, and card issuer which involve the bankcard inter-bank
transactions.
2 Normative references
The provisions in following documents become the provisions of this Standard
through reference in this Standard. For the dated references, the subsequent
amendments (excluding corrections) 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-1994 Bank card originated messages - Interchange message
specifications - Content for financial transactions (ISO 8583.1987, IDT)
GB/T 12406 Codes for the representation of currencies and funds
GB/T 20548 Retail financial services - Merchant category codes
GB/T 2659 Codes for the representation of names of countries and regions
GB/T 19584 Magnetic stripe data content and specification for bank card
GB 18030-2000 Information technology - Chinese ideograms coded
character set for information interchange - Extension for the basic set
JR/T 0025 (all parts) China financial integrated circuit card specifications
3 Terms and definitions
The following terms and definitions apply to this part.
3.1
Request message
Message generating a series of interactive messages.
Note. the completion of this action requires reply response.
3.2
Response message
The message used by the receiver of the original request or advice message
to notify the sender that this request message or advice message has been
received.
Note. This response indicates what actions the receiver has taken to
complete the original request or advice.
3.3
Advice message
The message used by the sender to notify the receiver of the actions that
had been taken, which does not require acknowledgement but requires
response.
4 Symbol
4.1 Data type symbol
The symbols appearing in this part are described in Table 1.
Unless otherwise specified, all message fields of fixed length in the data type
“n” are filled zero in front and right justified; other message fields of fixed lengths
are followed by spaces and left-justified. In the message fields of data types in
“b”, the 8-bit blocks are followed by zeros and left-justified. All message fields
are counted from left to right, i.e. the count of the leftmost position is 1.
The encoding method adopted by this specification is ASCII code.
6 Message header
The message header is the first part of the message.
6.1 Field descriptions
The message header defined in this part consists of 10 fields.
6.1.1 Field 1. Header-Length
- Attributes. b8, 8bit binary number;
- Producers. Institutions, switching center;
- Description. Number of bytes of message header stored in this field;
- Usage. Clearly identify the length of the message header;
- Field edit value. the value of this field must be 46;
- Reject code. 00015 = Illegal value.
6.1.2 Field 2. Header-Flag-and-Version
- Attributes. b8, 8bit binary number;
- Producers. Institutions, switching center;
- Description. The first digit from the left of the field is the header flag, which
means the following.
• 0 indicates that this message is a production message;
• 1 indicates that this message is a test message.
This bit is filled in by the originator of the transaction, it remains unchanged
during the transmission of the message.
The binary value of the last seven bits from the left of the field defines the
version of this message format.
- Reject code. 00025 = Illegal value.
6.1.3 Field 3. Total-Message-Length
- Attributes. n4, 4 bytes fixed-length numeric character;
- Reject code. 00065 = Illegal value.
6.1.7 Field 7. Batch-Number
- Attributes. b8, 8bit binary number;
- Producer. Switching center;
- Description. This field contains the lot number assigned by the switching
center for the message. Whenever a new request or advice is received by
the switching center, the current lot number is inserted into the field. If the
switching center receives a transaction-related transaction message, the
field value of this transaction is the same as that of the field of the original
transaction message;
- Usage. The value of this field is binary zero if it is a request message sent
by the institution. When the institution returns a reply to the switching center,
the value of this field is the same as that in its corresponding request
message.
- Field edit value. This field must be binary zero in the request message
generated by the institution.
- Reject code. 00075 = Illegal value.
6.1.8 Field 8. Transaction-Category-Identification
- Attributes. ans8,8 bytes of letters, numbers and special characters;
- Producers. Institutions, switching center;
- Description. Completed by the institution or the switching center, for the
purpose of differentiating transactions from different perspectives, to
facilitate the diversion of transactions between switching centers and
institutions. This part does not define the specific classification and
corresponding values.
- Field edit value. When the institution returns a reply to the switching center,
the value of this field is the same as that in its corresponding request
message.
- Reject code. 00085 = Illegal value.
6.1.9 Field 9. User-Information
- Attributes. b8, 8bit binary number;
- Field edit value. This field is filled with “0000” in the message header
generated by the institution. A detailed definition of reject code is shown in
Appendix A Reject code;
- Reject code. None.
6.2 Message header of normal message
The normal message has a message header.
6.3 Message header of reject message
The switching center will reject the request message with syntax error, add a
reject m...