JR/T Translated English of Chinese Standard: JR/T

Transcription

1 Translated English of Chinese Standard: JR/T Buy True-PDF Auto-delivery. JR FINANCIAL INDUSTRY STANDARD OF THE PEOPLE S REPUBLIC OF CHINA ICS Registration number JR/T Technical specifications on bankcard interoperability - Part 1: Message interface 银行卡联网联合技术规范 - 第 2 部分 : 报文交换 JR/T How to BUY & immediately GET a full-copy of this standard? Search --> Add to Cart --> Checkout (3-steps); 3. No action is required - Full-copy of this standard will be automatically & immediately delivered to your address in 0~60 minutes. 4. Support: Sales@ChineseStandard.net. Wayne, Sales manager Issued on: June 01, 2009 Implemented on: July 01, 2009 Issued by: People s Bank of China Buy True-PDF Auto-delivery. Page 1 of 95

2 Table of Contents Foreword Scope Normative references Terms and definitions Symbol Data type symbol Message format symbol Mandatory and conditional symbols of message fields Message structure Message header Field descriptions Message header of normal message Message header of reject message Message type Version number Message type flag Message bitmap Message field description Message field directory Field 2: Primary Account Number (PAN) Field 3: Processing code Field 4: Amount, Transaction Field 5: Amount, Settlement Field 6: Amount, Cardholder Billing Field 7: Transmission Date and Time Field 9: Conversion Rate, Settlement Field 10: Conversion Rate, Cardholder Billing Field 11: System Trace Audit Number Buy True-PDF Auto-delivery. Page 2 of 95

3 9.11: Time, Local Transaction Field 13: Date, Local Transaction Field 14: Date, Expiration Field 15: Date, Settlement Field 16: Date, Conversion Field 18: Merchant's Type Field 19: Acquiring Institution Country Code Field 22: Point of Service Entry Mode Code Field 23: Card Sequence Number Field 25: Function Code Field 26: Point of Service PIN Capture Code Field 28: Amount, Transaction Fee Field 32: Acquiring institute identification code Field 33: Forwarding Institution Identification Code Field 35: Track 2 Data Field 36: Track 3 Data Field 37: Retrieval Reference Number Field 38: Authorization Identification Code Field 39: Response Code Field 41: Card Acceptor Terminal Identification Field 42: Card Acceptor Identification Code Field 43: Card Acceptor Name/Location Field 44: Additional Response Data Field 48: Additional Data Private Field 49: Currency Code, Transaction Field 50: Currency Code, Settlement Field 51: Currency Code, Cardholder Billing Field 52: Personal Identification Number (PIN) Data Field 53: Security Related Control Information Buy True-PDF Auto-delivery. Page 3 of 95

4 9.40 Field 54: Additional Amounts Field 55: Integrated Circuit Card (ICC) System Related Data Field 57: Additional Data Private Field 58: IC (PBOC) Data Reserved Field 60: POS additional information Field 61: Cardholder Authentication Information Field 70: Network Management Information Code Field 90: Original Data Element Field 96: Message Security Code Field 100: Receiving Institution Identification Code Field 102: Account Identification Field 103: Account Identification Field 121: Switch Reserved Field 122: Acquiring Institution Reserved Field 123: Issuer Institution Reserved Field 128: Message Authentication Code Correlation of key information field to message Correlation of response message and request message Correlation of subsequent transactions and original transactions Message format description Financial transaction online message Management transaction online message Appendix A (Normative) Reject code Appendix B (Normative) Transaction type code Appendix C (Normative) Response code Appendix D (Informative) Transaction type distinction table References Buy True-PDF Auto-delivery. Page 4 of 95

5 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 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. Buy True-PDF Auto-delivery. Page 5 of 95

6 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 Bank card originated messages - Interchange message specifications - Content for financial transactions (ISO 8583:1987, IDT) GB/T Codes for the representation of currencies and funds GB/T Retail financial services - Merchant category codes GB/T 2659 Codes for the representation of names of countries and regions GB/T Magnetic stripe data content and specification for bank card GB 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. Buy True-PDF Auto-delivery. Page 6 of 95

7 Request message Message generating a series of interactive messages. Note: the completion of this action requires reply response. 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. 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. Buy True-PDF Auto-delivery. Page 7 of 95

8 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 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: = Illegal value 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: = Illegal value Field 3: Total-Message-Length - Attributes: n4, 4 bytes fixed-length numeric character; Buy True-PDF Auto-delivery. Page 11 of 95

9 - Reject code: = Illegal value 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: = Illegal value 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: = Illegal value Field 9: User-Information - Attributes: b8, 8bit binary number; Buy True-PDF Auto-delivery. Page 14 of 95

10 - 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 message header 3 in front of this request message, then return it to the sender of this message. Therefore, a message rejected by the switching center due to a syntax error (or failing to enter the subsequent processing flow due to switching center anomaly) has two message headers, the first header is the reject header, the field 10 of which indicates the reasons why this message is rejected, the second header is the header of the original message. Only switching centers can send messages with reject message header. An institution cannot send a message with a reject message header, that is, an institution can discard the error message of the switching center, but it cannot reject it. 7 Message type The message type is the second part of the message. It consists of two elements: the version number (see 7.1) and the message type flag (see 7.2). 7.1 Version number When there are a number of revisions in this revision of the standard, it is necessary to know the version information that created the message in the past in order to handle the message correctly. A version number shall be specified (see Table 4). Changes made to the text of standard content or code definitions do not cause a change in the version number. 3 The switching center will not modify any contents of the original message, but only add the reject message header in front of the original error message. Buy True-PDF Auto-delivery. Page 16 of 95

11 9.2.4 Reject code = Illegal character in length field: = Length value greater than 19; = Illegal character in primary account; 9.3 Field 3: Processing code Variable attributes n6, 6 bytes fixed-length numeric characters Field descriptions Transaction processing code is a numerical sequence used to describe the effect of a transaction and the account type which is affected. This field is composed of 3 parts, totally 6 positions: a) Transaction type code, an2; b) Account type code 1, an2; c) Account type code 2, an2. Transaction type code describes the specific transaction type (see Table B.1). Account type code 1 describes the FROM account type that affects debit, inquiry, and transfer. Account type code 2 describes the TO account type that affects credit and transfer. The first bit value of the FROM account type and the TO account type is as shown in Table B.2, and the second bit value is valued as shown in Table B Usage The field must match the request in the response. The field must be the same as the original transaction in the related transaction Reject code = Illegal transaction code or illegal characters. Buy True-PDF Auto-delivery. Page 23 of 95

12 of the decimal point. If the first digit is 8, there shall be a 0 after the decimal point; if the first digit is 9, there shall be two 0 after the decimal point Usage This field is filled by the switching center. This field appears only if the transaction currency (field 49) is different from the settlement currency (field 50) Reject code = Illegal character. 9.9 Field 10: Conversion Rate, Cardholder Billing Variable attributes n8, 8 bytes fixed-length numeric characters Field descriptions Conversion ratio from the transaction currency to the cardholder account currency. The leftmost digit indicates the number of digits the decimal separator shall move from right to left. The second to the eighth bit is the ratio, for example, the conversion ratio of is equal to , up to 9 digits to the right of the decimal point. If the first digit is 8, there shall be one 0 after the decimal point; if the first digit is 9, there shall be two 0 after the decimal point Usage This field is filled by the switching center. This field appears only if the transaction currency (field 49) differs from the cardholder account currency (field 50) Reject code = Illegal character Field 11: System Trace Audit Number Variable attributes Buy True-PDF Auto-delivery. Page 27 of 95

13 9.12 Field 13: Date, Local Transaction Variable attributes n4, 4 bytes fixed-length numeric characters. Format: MMDD Field descriptions At the time of the transaction, the date on which the cardholder is located Usage The fields in the request message and response message remain unchanged. Due to abnormal transactions, in the follow-up transactions automatically triggered by the system (such as reversal), the field shall be consistent with the original transaction Reject code = Illegal number or character Field 14: Date, Expiration Variable attributes n4, 4 bytes fixed-length numeric characters. Format: YYMM Field descriptions The expiration date of the bankcard. For example: the value of this field is 1005, indicating that the card is valid from May 2010, then from June 1, 2010 the card is an expired card Usage Bank card valid period Reject code = Illegal number or character. Buy True-PDF Auto-delivery. Page 29 of 95

14 Reject code = Illegal number or character Field 18: Merchant's Type Variable attributes n4, 4 bytes fixed-length numeric characters Field descriptions Represents the MCC (Merchant Category Code) Usage The merchant type code indicates the service range and attributes of the merchant. It must appear in the 01XX, 02XX, 04XX messages, filled by the initiator of the transaction, and shall remain unchanged throughout the life of the transaction. This field values follow GB/T Reject code = Illegal characters Field 19: Acquiring Institution Country Code Variable attributes n3, 3 bytes fixed-length numeric characters Field descriptions The country code of the acquiring institution. See GB/T 2659 Codes for the representation of names of countries and regions Usage Filled by the receiver, indicating the code of the country to which the acquiring institution belongs Reject code = Illegal characters. Buy True-PDF Auto-delivery. Page 31 of 95

15 2-9 bytes: It means that the cardholder's transaction fee amount that shall be debited or credited Reject code = Non-numeric character Field 32: Acquiring institute identification code Variable attributes n..11 (LLVAR), 2-byte length value + maximum 11-byte acquiring institute identification code Field descriptions The code used to identify the acquirer. This field value shall be identified in accordance with the relevant standard 4 ; Usage The field shall be consistent in the request message and response message. The field shall be consistent in the related transactions (such as reversal, revocation) and its original transaction message. The combination of this field with the field 7, 11, 33 uniquely identifies a transaction Reject code = Illegal character in length field = Length value is greater than Field 33: Forwarding Institution Identification Code Variable attributes n..11 (LLVAR), 2 bytes length value + maximum 11 bytes forwarding institution identification code. 4 Refer to China UnionPay Co., Ltd. Q/CUP Network access institute identification code. Buy True-PDF Auto-delivery. Page 35 of 95

16 Reject code = Illegal character in length field; = Length value greater than 37; = Illegal track 2 content or illegal characters Field 36: Track 3 Data Variable attributes z (LLLVAR), 3 bytes length value + track 3 data up to 104 bytes (characters) Field description The track 3 data on the card. This field value shall follow the GB/T Code for the bank card magnetic stripe information format and use Usage It reads from the first character after the start character (;) of the track 2, including the separator for the field, excluding the end character and the LRC character. This field does not appear in advice transactions Reject code = Illegal character in length field; = Length value is greater than 104; = Illegal track 3 content or illegal characters Field 37: Retrieval Reference Number Variable attributes an12, 12-byte fixed-length alphanumeric characters Field description Buy True-PDF Auto-delivery. Page 37 of 95

17 an2, 2-byte fixed-length alphanumeric characters Field descriptions Code defined for the actions had been taken or to be taken, and why they are taken Usage For each received request message, the issuer shall return the result processed by this system to the acquirer in this field. When the switching center cannot forward the message to the issuer, the switching center will directly respond to the acquirer. The response code is defined in Appendix C Reject code = Illegal characters Field 41: Card Acceptor Terminal Identification Variable attributes ans8, 8-byte fixed-length alphanumeric and special characters Field descriptions If the card acceptor terminal identification code is less than 8 bytes, it is stored from left side, and filled with spaces at right side Usage This identification code must uniquely identify a terminal in the acquirer's network. In all bank card transactions, the field must appear and remain unchanged throughout the transaction cycle Reject code = Illegal characters. Buy True-PDF Auto-delivery. Page 39 of 95

18 9.33 Field 44: Additional Response Data Variable attributes ans..25 (LLVAR), 2 bytes length value + additional response data up to 25 bytes (letters, numbers and special characters) Field descriptions Identifier assigned by the issuer to the approved transaction. This field can be used by the issuer to identify the original transaction Usage This field is a card issuer optional field. The issuer's additional response data must be a valid character. The response message is loaded by the issuer when approving a transaction. The acquirer and switching center will not process this field. If a reversal is needed to be initiated after receiving the response message as approved by the card issuer, the value of this field in the original response message needs to be sent to the card issuer Reject code = Illegal character in length field; = Length value is greater than Field 48: Additional Data Private Variable attributes ansb (LLLVAR), 3 bytes length value + initiator additional data up to 999 bytes (letters, numbers, special characters, binary numbers) Field descriptions This part only defines the format of the field; however, it does not specify the specific value. Regardless of how the parties to the transaction agree on the value of this field, the following basic format requirements shall be followed: Buy True-PDF Auto-delivery. Page 41 of 95

19 It refers to the type of the currency used by the 4 th field (transaction amount), the specific value is as shown in GB/T Usage Generally, this field is filled by the acquirer. This field must be present when field 4 (Transaction Amount) appears Reject code = Illegal characters Field 50: Currency Code, Settlement Variable attributes an3, 3-byte fixed-length alphanumeric characters Field descriptions It refers to the type of the currency used by the 5 th field (settlement amount), the specific value is as shown in GB/T Usage This field is filled by the switching center. This field must appear when the 5 th field (settlement amount) appears Reject code = Illegal code Field 51: Currency Code, Cardholder Billing Variable attributes an3; 3-byte fixed-length alphanumeric characters Field descriptions It refers to the type of the currency used by the 6 th field (cardholder billing amount), the specific value is as shown in GB/T Usage Buy True-PDF Auto-delivery. Page 43 of 95

20 Field descriptions This field will contain different sub-fields depending on the type of transaction. The processing center passes only those specific data applicable to IC card transactions between the acquirer and the issuer, without any modification or processing. To adapt to the changing needs of the sub-field, the field uses the tag-length-value (TLV) representation, that is, each sub-field is composed of tag (T), sub-field value length (L), and sub-field value (V). The tag attribute is bit, expressed by hexadecimal, accounting for 1 ~ 2 bytes in length. For example, 9F33 is a tag that occupies two bytes, while 95 is a tag that occupies one byte. If the last five bits of the first byte of the tag (Note: the byte ordering direction is from left to right, the first byte is the leftmost byte. Bit is ordered by the same rules) is 11111, then the tag occupies two bytes, for example, 9F33 ; otherwise, it occupies one byte, for example, 95. The attribute of the sub-field length (i.e., L itself) is also bit, accounting for 1 ~ 3 bytes. The specific coding rules are as follows: a) When the leftmost bit (i.e., bit8) of the leftmost byte of the L field is 0, it indicates that the L field occupies one byte, and the following seven bits (i.e., bit7 ~ bit1) indicate the length of the subfield value, a decimal number indicates the decimal number of the length of the subfield. For example, if a field takes 3 bytes, the value length of its subfield is expressed as Therefore, if the length of the subfield is between 1 and 127 bytes, the L field itself occupies only one byte. b) When the leftmost bit (i.e., bit8) of the leftmost byte of the L field is 1, indicating that the L field occupies more than one byte, the number of bytes occupied by it is indicated by the decimal value of the last 7 bits (i.e., bit7 ~ bit1) of the leftmost byte. For example, if the leftmost byte is , it means that the L field is followed by two bytes, in addition to the byte. The decimal value of the subsequent byte indicates the length of the subfield value. For example, if the L field is , this subfield takes 255 bytes. Therefore, if the value of the subfield is between 128 and 255 bytes, then the L field needs to occupy two bytes. Subfields take different values depending on the meaning of different subfields. Since the sub-fields contained in the field are all information unique to the IC card and the IC card terminal rather than the characteristic information of the processing center, the processing center is only a bridge for data transmission, so the specific values are as shown in JR/T This specification only gives tag, length value and its attributes. The definition of each sub-field is as shown in Appendix A of JR/T Buy True-PDF Auto-delivery. Page 47 of 95

21 - <Formatter>; Description of the follow-up data, the length is 2 bytes. - <Data>; Specific data, the format depends on the <formatter> characters, the maximum length is not more than 997 bytes Usage This transaction is agreed upon by the parties to the transaction. This field is only allowed to appear in the transaction response message, but not in the transaction request message Reject code = Illegal character in length field; = Length value is greater than 999; = Illegal character Field 58: IC (PBOC) Data Reserved Attributes ans (LLLVAR), 3-byte length value + up to 999 bytes (letter, numeric characters, special symbols) transaction data Field descriptions None Usage Reserved for PBOC e-wallet / passbook IC card transaction Reject code = Illegal characters in length field: = Length value greater than 999; = Illegal character. Buy True-PDF Auto-delivery. Page 50 of 95

22 Field descriptions The new key assigned by the switching center to the institution Usage This field only appears in the reset key message actively initiated by the switching center, it is filled in by the switching center. The institution shall activate the key once it is received Reject code None Field 100: Receiving Institution Identification Code Variable attributes n..11 (LLVAR), 2 bytes length value + receiving institution identification code of up to 11 bytes Field descriptions The field is used to identify the code of the receiving institution. The receiving institution is the institution that accesses the switching center directly. The value of this field shall be identified in accordance with the relevant standard Usage This field is filled by the switching center Reject code = Illegal character in length field; = Length value is greater than Field 102: Account Identification Variable attributes 7 Currently refer to China UnionPay Co., Ltd. Q/CUP Network access institution identification code. Buy True-PDF Auto-delivery. Page 56 of 95

23 ans (LLLVAR), 3 bytes length + switching center reserved information up to 999 bytes (numeric, letters and special characters) Field description Reserved for the switching center to define Usage Reserved for the switching center to define Reject code = Illegal characters in length field: = length value is greater than 999; = Illegal character Field 122: Acquiring Institution Reserved Variable attributes an..999 (LLLVAR), 3 bytes length value + acquirer reserved information up to 999 bytes (numeric, letters, and special characters) Field description Reserved for the acquirer to define Usage Reserved for the acquirer to define Reject code = Illegal characters in length field: = length value is greater than 999; = Illegal character Field 123: Issuer Institution Reserved Variable attributes Buy True-PDF Auto-delivery. Page 58 of 95

24 10 Correlation of key information field to message The Key Field is used to identify a transaction. Issuer, switching center and acquirer of key field related transactions use the request and response of the key field related transaction, the original transaction and subsequent related transactions. This chapter defines key information fields through which the request message and response message, the subsequent transactions and the original transaction are associated Correlation of response message and request message The switching center and the institution shall correlate the original request transaction by the field 7 (transaction transmission time), field 11 (system tracking number), field 32 (acquiring institution identification code) and field 33 (forwarding institution identification code) in the response message Correlation of subsequent transactions and original transactions Correlation between reversal transaction and original transaction Switching centers and institutions shall correlate the original transaction by the field 90 (original data elements) in the reversal transaction Correlation between consumption revocation and consumption The switching centers and institution shall correlate the original consumption transaction by the field 90 (original data elements) in the consumption revocation transaction Correlation between pre-authorization revocation and pre-authorization The switching center and the institution shall correlate the original preauthorization transaction by the field 2 (primary account), field 38 (authorization identification response code), field 42 (card identification number) in the preauthorization transaction Correlation between pre-authorization completion and pre-authorization Buy True-PDF Auto-delivery. Page 60 of 95

25 Appendix A (Normative) Reject code The reject code consists of 5 bits. The first bit represents the location where the error occurred. A value of 0 indicates an error in the header field. A value of 1 indicates that the message body field has an error. A value of 2 indicates that the transaction is rejected due to a switching center. When the first bit is 0 or 1, the last 3 bits indicate the message field where the error occurred, and the last bit is the error type. When the first bit is 2, the last four bits indicate the error reason. A.1 Error type code table When the 1 st bit of the reject code is 0 (error occurs in the message header message field) or 1 (error occurs in the message body message field), it indicates the error type of this message field. Error type 0 Reserved for industry use Table A.1 -- Error type table Error descriptions 1 The total length of the message field is incorrect 2 Bit map is illegal, the message field XXX shall not exist (e.g. 0052, the message field 5 as not defined by this system appears) 3 Illegal characters appear in the length field 4 Length value is greater than a specific value 5 Illegal character occurs / illegal content 6 Missing necessary message fields 7-8 Reserved for industry use 9 Reserved for private use Error type 2 and error type 6 may appear for each field, they are no longer listed in the following tables of this clause. A.2 Message header message field reject code table Table A.2 -- Message header message field reject code table Reject code Message field number Error type Error descriptions Illegal characters appear in the header length Illegal characters appear in header flag and version Non-numeric characters appear in the total length of message Illegal characters appear in destination ID Buy True-PDF Auto-delivery. Page 84 of 95

26 Appendix B (Normative) Transaction type code Table B.1 lists the Transaction type codes, Table B.2 lists the Account type codes, which together form the processing code. Table B.1 -- Transaction type code Range Code Descriptions 00 Goods and services 01 Cash withdrawal / cash payment Adjustment Debit Reserved for private use Reserved for industry use 19 Charging 20 Refund 21 Deposit 22 Adjustment Reserved for industry use Credit Reserved for private use Reserved for industry use 29 Payment 30 Inquiry available balance Inquiry balance Inquiry Reserved for industry use service Reserved for private use Reserved for industry use 40 Cardholder account transfer Reserved for private use Transfer 46 Transfer-out service 47 Transfer-in Reserved for industry use Reserved for private use Reserved for industry use Reserved Reserved for private use Reserved for industry use Table B.2 -- The 1 st bit of account type The 1 st bit Descriptions Meanings 0 Default Default 1 Saving account Saving account 2 Cheque account Cheque account 3 Credit facility Credit facility 4 Universal account number Universal account number 5 Investment account Investment account Buy True-PDF Auto-delivery. Page 88 of 95

27 Appendix C (Normative) Response code Used for the field 39 in the message, indicating the result of the transaction processing. Table C.1 -- Response code table Code Meaning Action 00 Acceptance or transaction succeeds Approved 01 Check card issuer Rejected 02 Check card issuer special conditions Rejected 03 Invalid merchant Rejected 04 Card confiscated Rejected and card confiscated 05 Acceptance rejected Rejected 06 Error Rejected 07 Card confiscated under special conditions Rejected and card confiscated 08 Reserved for industry use - 09 Request in processing Rejected 10 Partial amount approved Approved 11 Approved by important person (VIP) Approved 12 Invalid transaction Rejected 13 Invalid amount Rejected 14 Invalid card number (account not available) Rejected 15 Card issuer not available Rejected 16 Track 3 update approved Approved 17 Rejected but card not confiscated Rejected 18 Reserved for industry use - 19 Send for transaction again Rejected 20 Invalid response Rejected 21 Action cannot be taken Rejected 22 Fault suspected Rejected 23 Transaction fee unacceptable Rejected 24 Reserved for industry use - 25 Original transaction cannot be found Rejected Reserved for industry use - 30 Format wrong Rejected 31 Bank unsupported by the switching center Rejected 32 Reserved for industry use - 33 Expired card Rejected 34 Suspected of cheating Rejected and card confiscated 35 Card acceptor contacts with the acquirer (card confiscated) Rejected and card confiscated 36 Restricted card Rejected and card confiscated Buy True-PDF Auto-delivery. Page 90 of 95

28 Appendix D (Informative) Transaction type distinction table D.1 Financial transactions Table D.1 -- Online transaction type distinction table Transaction type Message type Value of field (request / response) 3 Value of field 25 Balance inquiry 0200/ x000 00/02 Cash withdrawal 0200/ x000 00/02 Cash withdrawal reversal 0420/ x000 00/02 Pre-authorization 0100/ x Pre-authorization revocation 0100/ x Pre-authorization reversal 0420/ x Pre-authorization revocation reversal 0420/ x Pre-authorization completion (request) 0200/ x Pre-authorization completion (advice) 0220/ x Pre-authorization completion revocation 0200/ x Pre-authorization completion reversal 0420/ x Pre-authorization completion revocation reversal 0420/ x Consumption 0200/ x Consumption reversal 0420/ x Consumption revocation 0200/ x Consumption revocation reversal 0420/ x Return (online) 0220/ x Transfer 0200/ x Transfer-out 0200/ x Transfer-in 0200/ x Transfer-out reversal 0420/ x Transfer-in confirmation 0220/ x D.2 Management transactions Table D.2 -- Application management and reconciliation transaction type classification table Transaction type Reset key Daily cutoff advice Transaction name Message type (request/response) Value of field 70 Apply to rest key (initiated by institution) 0820/ Reset key (initiated by centre) 0800/ Daily cutoff start 0820/ Daily cutoff end 0820/ Buy True-PDF Auto-delivery. Page 93 of 95