Today, I passed Google, in a forum, a post about 8583 packs, written very well, here is thankful to this prawn! I raised this post on the format, making it a bit more clear. The following is the specific content:
ISO8583 package (referred to as 8583 package) is an international standard package format, up to 128 field domains, each domain has a unified regulation, and has a minimum and growing. The 8583 package is a bitmap, used to determine the field of field domains of the package. The bitmap is the soul of the 8583 package, which is the key to packaged unpacking the field domain, and understanding the properties of each field domain is the basis for filling the data.
1. The bitmap is described below: Bitmap Location: 1 Format: Type: B16 (Binary 16 Bit, 16 * 8 = 128bit) Description: If you set the first bit of bitmap to '1', it means using an extension bit. Figure (128 domain), otherwise it means only the basic bitmap (64 domains). If a data field is used, the corresponding bit is set to '1', such as using a 41 domain, you need to set the 41 bit of the bitmap to '1'. Selecting conditions: If you use 65 to 128 domain, you need to set the first bit of the domain to '1'.
2, the definition of each domain is as follows: typedef struct iso8583 {int bit_flag; / * Domain data type 0 - String, 1 - int, 2 - binary * / char * data_name; / * Domain name * / int LENGTH; / * Data domain length * / int LENGTH_IN_BYTE; / * The actual length (if it is long) * / int variable_flag; / * Whether it becomes a long flag 0: No 2: 2 Bits become long, 3: 3 bits "/ int Dattyp ; / * 0 - String, 1 - INT, 2 - binary * / char * data; / * Store specific value * / int attribute; / * reserved * /} ISO8583;
ISO8583 TBL8583 [128] = {/ * FLD 1 * / {0, "Bit Map, Extended", 8, 0, 0, 2, NULL, 0}, / * fld 2 * / {0, "Primary Account Number" , 22, 0, 2, 0, null, 0}, / * FLD 3 * / {0, "Processing Code", 6, 0, 0, 0, NULL, 0}, / * FLD 4 * / {0, "Amount, Transaction", 12, 0, 0, 1, NULL, 0}, / * fld 5 * / {0, "NO USE", 12, 0, 0, 0, NULL, 0}, / * FLD 6 * / {0, "NO USE", 12, 0, 0, 0, NULL, 0}, / * fld 7 * / {0, "Transaction Date and Time", 10, 0, 0, 0, NULL, 0 }, / * FLD 8 * / {0, "NO USE", 8, 0, 0, 0, NULL, 0}, / * FLD 9 * / {0, "NO USE", 8, 0, 0, 0 , NULL, 0}, / * FLD 10 * / {0, "NO USE", 8, 0, 0, 0, NULL, 0}, / * FLD 11 * / {0, "System TRACE Audit Number", 6 , 0, 0, 1, NULL, 0}, / * FLD 12 * / {0, "Time, Local Transaction", 6, 0, 0, 0, NULL, 0}, / * fld 13 * / {0, "DATE, LOCAL Transaction", 4, 0, 0, 0, NULL, 0}, / * fld 14 * / {0, "DATE, EXPIRATION", 4, 0, 0, 0, NULL, 0}, / * FLD 15 * / {0, "Date, Settlement", 4, 0, 0, 0, NULL, 0}, / * fld 16 * / {0, "NO USE", 4, 0, 0, 0, NULL, 0}, / * fld 17 * / {0, "DATE, CAPTURE", 4, 0, 0, 0, NULL, 0} , / * FLD 18 * / {0, "Merchant's Type", 4, 0, 0, 0, NULL, 0}, / * FLD 19 * / {0, "NO USE", 3, 0, 0, 0, NULL, 0}, / * FLD 20 * / {0, "NO USE", 3, 0, 0, 0, NULL, 0}, / * fld 21 * / {0, "NO USE", 3, 0, 0, 0, NULL, 0}, / * fld 22 * / {0, "Point of Service Entry Mode", 3, 0, 0, 0, NULL, 0}, / * fld 23 * / {0, "NO Uses ", 3, 0, 0, 0, null, 0}, / * fld 24 * / {0," NO USE ", 3, 0, 0, 0, NULL, 0}, / * FLD 25 * / { 0, "Point of Service Condition Code", 2, 0, 0, 0, NULL, 0}, / * FLD 26 * / {0, "NOSE", 2, 0, 0, 0, NULL, 0}, / * FLD 27 * / {0, "NO USE"
, 1, 0, 0, 0, NULL, 0}, / * fld 28 * / {0, "Field27", 6, 0, 0, 0, NULL, 0}, / * fld 29 * / {0, " No use ", 8, 0, 1, 0, null, 0}, / * fld 30 * / {0," no use ", 8, 0, 1, 0, null, 0}, / * FLD 31 * / {0, "NO USE", 8, 0, 1, 0, NULL, 0}, / * fld 32 * / {0, "AcquiR Institution ID. Code", 11, 0, 2, 0, NULL, 0} , / * FLD 33 * / {0, "Forwarding Institution ID. Code", 11, 0, 2, 0, NULL, 0}, / * FLD 34 * / {0, "NO USE", 28, 0, 2 , 0, NULL, 0}, / * FLD 35 * / {0, "Track 2 Data", 37, 0, 2, 0, NULL, 0}, / * FLD 36 * / {0, "Track 3 Data" , 104, 0, 3, 0, null, 0}, / * fld 37 * / {0, "Retrieval Reference Number", 12, 0, 0, 0, NULL, 0}, / * FLD 38 * / {0 , "Auth. Identification Response", 6, 0, 0, 0, NULL, 0}, / * fld 39 * / {0, "Response Code", 2, 0, 0, 0, NULL, 0}, / * FLD 40 * / {0, "NO USE", 3, 0, 0, 0, NULL, 0}, / * FLD 41 * / {0, "Card Acceptor Terminal ID.", 8, 0, 0, 0, NULL, 0}, / * fld 42 * / {0, "Card Acceptor Identification Code", 15, 0, 0, 0, NULL, 0}, / * FLD 43 * / {0, "Card Acceptor Name Location", 40, 0, 0, 0, null, 0}, / * fl D 44 * / {0, "Additional Response Data", 25, 0, 2, 0, NULL, 0}, / * FLD 45 * / {0, "NO USE", 76, 0, 2, 0, NULL, 0}, / * FLD 46 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * fld 47 * / {0, "Field47", 999, 0, 3, 0 , NULL, 0}, / * FLD 48 * / {0, "Additional Data --- Private", 999, 0, 3, 0, NULL, 0}, / * fld 49 * / {0, "Currency Code, Transaction ", 3, 0, 0, 0, null, 0}, / * fld 50 * / {0," currency code, settlement ", 3, 0, 0, 0, null, 0}, / * fld 51 * / {0, "NO USE", 3, 0, 0, 0, NULL, 0}, / * fld 52 * / {0, "Personal Identification Number Data"
, 8, 0, 0, 2, null, 0}, / * fld 53 * / {0, "Security Related Control Information", 16, 0, 0, 0, NULL, 0}, / * FLD 54 * / { 0, "Additional Amounts", 120, 0, 3, 0, NULL, 0}, / * FLD 55 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 56 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * fld 57 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0} , / * FLD 58 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 59 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 60 * / {0, "NO USE", 5, 0, 3, 0, NULL, 0}, / * FLD 61 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 62 * / {0, "NO USE", 11, 0, 3, 0, NULL, 0}, / * FLD 63 * / {0, "NO USE", 11, 0, 3, 0, null, 0}, / * fld 64 * / {0, "Message Authentication Code Field", 8, 0, 0, 2, NULL, 0}, / * FLD 65 * / {0 , "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 66 * / {0, "NO USE", 1, 0, 0, 0, NULL, 0}, / * FLD 67 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 68 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 69 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 70 * / {0, "System Management Information Code", 3, 0, 0, 0, NULL, 0}, / * fld 71 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 72 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 73 * / {0, "NO USE", 6, 0, 0, 0, NULL, 0}, / * fld 74 * / {0, " Number of crdits ", 10, 0, 0, 0, null, 0}, / * fld 75 * / {0," Reversal Number of Credits ", 10, 0, 0, 0, NULL, 0}, / * fld 76 * / {0, "Number of Debits", 10, 0, 0, 0, NULL, 0}, / * fld 77 * / {0, "Reversal Number of Debits", 10, 0, 0, 0, NULL , 0}, / * FLD 78 * / {0, "Number of Transfer", 10, 0, 0, 0, NULL, 0}, / * FLD 79 * / {0, "Reversal Number of Transfer"
, 10, 0, 0, 0, NULL, 0}, / * FLD 80 * / {0, "Number of Inquirs", 10, 0, 0, 0, NULL, 0}, / * FLD 81 * / {0 , "Authorization Number", 10, 0, 0, 0, NULL, 0}, / * fld 82 * / {0, "NOSE", 12, 0, 0, 0, NULL, 0}, / * FLD 83 * / {0, "Credits, Transcation Feeamount", 12, 0, 0, 0, NULL, 0}, / * FLD 84 * / {0, "NO USE", 12, 0, 0, 0, NULL, 0 }, / * FLD 85 * / {0, "Debits, Transcation FeEamount", 12, 0, 0, 0, NULL, 0}, / * FLD 86 * / {0, "Amount of Credits", 16, 0, 0, 0, NULL, 0}, / * fld 87 * / {0, "Reversal Amount of Credits", 16, 0, 0, 0, NULL, 0}, / * fld 88 * / {0, "Amount of Debits ", 16, 0, 0, 0, null, 0}, / * fld 89 * / {0," Reversal Amount of Debits ", 16, 0, 0, 0, NULL, 0}, / * FLD 90 * / {0, "Original Data Elements", 42, 0, 0, 0, NULL, 0}, / * FLD 91 * / {0, "File Update Code", 1, 0, 0, 0, NULL, 0} , / * FLD 92 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 93 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * fld 94 * / {0, "Service Indicator", 7, 0, 0, 0, NULL, 0}, / * fld 95 * / {0, "Replacement Amounts", 42, 0, 0, 0, NULL, 0} , / * FLD 96 * / {0, "NO USE", 8, 0, 0, 0, NULL, 0}, / * fld 97 * / {0, "Amount of Net Settlement", 16, 0, 0, 0, NULL, 0}, / * FLD 98 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 99 * / {0, "SETLEMENT Institution ID", 11 , 0, 2, 0, NULL, 0}, / * FLD 100 * / {0, "Recveing Institution ID", 11, 0, 2, 0, NULL, 0}, / * FLD 101 * / {0, " Filename ", 17, 0, 2, 0, null, 0}, / * fld 102 * / {0," Account Identification1 ", 28, 0, 2, 0, NULL, 0}, / * FLD 103 * / { 0, "Account Identification2", 28, 0, 2, 0, NULL, 0}, / * FLD 104 * / {0, "NO USE"
, 999, 0, 3, 0, NULL, 0}, / * FLD 105 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 106 * / {0, "No USE", 999, 0, 3, 0, NULL, 0}, / * FLD 107 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 108 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 109 * / {0, "NO Use", 999, 0, 3, 0, NULL, 0}, / * FLD 110 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 111 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 112 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * fld 113 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 114 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 115 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 116 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * fld 117 * / {0, "NO USE ", 999, 0, 3, 0, null, 0}, / * fld 118 * / {0," NO USE ", 999, 0, 3, 0, NULL, 0}, / * FLD 119 * / {0 , "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 120 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 121 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 122 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 123 * / {0, "New Pin Data", 8, 0, 3, 2, NULL, 0}, / * FLD 124 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 125 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 126 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * fld 127 * / {0, "NO USE", 999, 0, 3, 0, NULL, 0}, / * FLD 128 * / {0, "Message Authentication Code Field", 8, 0, 0, 2, NULL, 0},}
3, become long, the length of the length, if the second domain: the domain name is the primary account, the data type is a String length 22 (which is not exceeding this) is a 2-bit change, because it is 2 bits, in the package The actual length of the data is required before the data domain, if it is 19 bits, it is represented as: 19 data value (ie the first two digits length), such as the third domain: the domain is the processing code, the data type is String length 6 It is a fixed length that must be filled with 6 bits. Addition A: ISO8583 Description 1, information type (Message Type) Defines a bitmap location: The data type is set by the initiator of the packet. The following requirements should be followed: The packet start section must be a type of information; a refusal answer can be given to the unsupported information type. 0100 Authorized Trading 0110 Authorized Trading Answer 0200 Financial Transaction 0210 Financial Transaction Reply 0240 Query Transaction 0250 Query Trading Answer 0400 Raise Transaction 0410 Raise Transaction Reply 0800 Management Transaction 0810 Management Transaction Reply 2, Bit Map - Basic Bitmap and Extended bitmap bitmap location: 1 format: Type: B16 Description: If the first bit of the bitmap is set to '1', the use of the extended bitmap, otherwise it means only the basic bitmap. If a data field is used, the corresponding bit is set to '1', such as using a 41 domain, you need to set the 41 bit of the bitmap to '1'. Selection conditions: If you use 65 to 128 domain, you need to set the domain to '1' 3, bit02 primary account (Primary Account Number)
Bitmap location: 02 Format: Growth, LLVAR Type: N..22 Description: Unique to confirm the basic account of a user transaction. Since the bank electronic service system involves multiple application systems, the account length is up to 22 bits, so the 19 length of the original standard is changed to 22 bits. 4, Bit03 Processing Code) Bitmap Location: 03 Format: Performance Type: N6 Description: The code used to describe how the transaction affects the customer account. Processing code and information codes together can uniquely define a type of transaction. Processing code consists of the following three parts: Location Description 1-2 Trading Action Code 3-4 Pay Account Types, for debit classes, such as queries, charges, and transactions. 5-6 Income account type, used for charge, transfer, etc. Among them: FF: Pay Account TT: Income Account * Determine 5, Bit04 Trading Amount (Amount, Transaction) Bitmap Location: 04 Format: Settlement Type: N12 Description: Account people require transaction amount, excluding any Processing and transaction costs. The amount of the amount and the currency code should be able to indicate the minimum unit of the corresponding currency. ISO4217 related currency code definitions. Such as "000000000100" is used to represent the US dollar, indicating 1.00 yuan; For trading such as queries, the transaction amount should be "00000000000000". 6, BIT06 Trading Date and Time (Transmission Date and Time) Bitmap Location: 07 Format: Performance, MMDDHMMSS Type: N10 Description: Local Trading Date and Time 7, Bit11 System Tracking No. (Systems Trace Audit Number) Bitmap Location: 11 Format: Type: N6 Description: Tracking number of terminal transactions. The transaction initiates the terminal filled out, and "Trading Date, Time", the information type, etc., can only define the only transaction of a terminal. That is to say, on the same day, the system tracking number of the same type of transaction should be different. The system tracking number cannot be modified during the transaction process. Use this domain to match the return of requests and notification classes. The application system uses this domain to check if the received license, financial, automatic, settlement, management, and network management, such as the response package of the network management, etc. Is its request package response. The system tracking number is not used to match the automatic key transaction, nor does it be used to match the previous pre-authorized transactions when pre-authorized consumption. Non-90 domain. For the bank electronic service system, the system tracking number is the transaction number. 8, BIT12 Local Trading Time (Time, Local Transaction) Bitmap Location: 12 Format: Pixabay, HHMMSS Type: N6 Description: The time taken on the terminal. Local trading hours cannot change during transaction processing. The local trading time cannot be changed when automatic rush is forwarded. 9, BIT13 Local Trading Date (Date, Local Transaction) Bitmap Location: 13 Format: Type: MMDD Type: N4 Description: The time taken on the terminal. The local trading time cannot be changed, and the local trading time cannot be changed when the transaction is stored, and the local trading time cannot be changed.
10, Bit14 Validity (DATE, Expiration) Bitmap Location: 14 Format: Setting: YYMM Type: N4 Description: The validity period of the card, the monthly month difference due to the card class write magnetic format, the validity period of the number of orders may not increase the card The authorization agency extracts the validity period of the card from the two tracks. Such as cards are no-two-track, the pending should require the validity period of manual entry card. Select conditions: 100, 200, 400 and other trading, if there is no 2, 3 track, must have this domain. 11, Bit15 settlement date (Date, Settlement) Bitmap location: 15 Format: Performance, MMDD Type: N4 Description: Bank electronic service system and host settlement time, format monthly day. The transaction that occurs before the date of checkout, participate in the day settlement. At the time of settlement, the checkout date is also used to calculate processing, transaction costs. 12, Bit17 Get Date (Date, Capture) Bitmap Location: 17 Format: Performance, MMDD Type: N4 Description: Get the accounting date of the transaction from the host. Usually used for hosts and merchants clearing. 13, Bit18 Merchant Type (Merchant's Type) Bitmap Location: 18 Format: Type: N4 Description: Define the code merchant type of the merchant product and service type for finance, authorized transactions, used to specify the type of service point. It mainly has the following uses: the maximum time to determine the pre-authorization transaction; control the legal limit; to control the transaction authorization, control network operation rules; fraud testing; for merchant classification reports; transaction cost processing. According to ISO8583 standard, the corresponding national standard should be used. Merchant type code table: Merchant type code industry Type Description 4215 Postal Service 4511 Civil Aviation 4722 Travel 4782 Parade 4789 Other Transportation Service 4614 Telecom Service 5542 Gas Station 5812 Restaurant 5999 Shopping 6010 Financial Institution - Artificial Cash Payment 6011 Financial Institution - Automatic Cash Payment 6012 Financial Institutions - All kinds of services 7011 hotels, hotel 7299 All kinds of personal services: Laundry, beauty, 7399 all kinds of business services: parking, car rental, advertising, other services 7699 all kinds of repair services: repair, car wash, trailer 7996 entertainment : Movies, Theater, Sports, Games 8099 Medical Services 8111 Legal Services 8999 Various Professional Services: Accounting, Education, Decoration, Engineering Selection Conditions: Delivery Terminal Lifting Transactions Be sure to have this domain. 14, bit22 Service Point Input Mode (Point-of-Service Entry Mode) Bitmap Location: 22 Format: Type: N3 Description: Define the input mode of the PIN and PAN on the service terminal. The service point input mode includes the following two aspects: Location Description 1-2 In the service terminal PAN validity period input mode 3-3 Input mode of input mode PAN on the service terminal PAN is encoded as follows: PAN input mode Description 00 I don't know 01 Handmade 02 Magnetic Card 03 Barcode Scanner (BAR) 04 Optical Symbol Reader (OCR) 05 Integrated Circuit Card (IC Card) PIN Input Method Coding As follows: PIN Input Method Description 0 I don't know 1 terminal can receive the PIN 2 terminal Can not receive PIN Selection Condition: The transaction initiated by the service point terminal must have this domain.
15, bit25 Service Code Code Bitmap Location: 25 Format: Type: N2 Description: Defining the service point type usage of the transaction occurred: The following is the service point condition code supported by Cyberbank. Service Point Condition Code Service Point Terminal Type 2 ATM (ATM) 10 Bank Terminal (10) 14POS 20 Phone Bank 16, Bit32 Labor IdiTification Data Code: 32 Format: LLVAR Type: n .. 11 Description: In financial transactions, this domain represents the identification codes of the banking mechanism that the transaction occurred must be the same as the request packet. 17, BIT3 forwarding code code code bitmap location: 33 Format: LLVAR type: n..11 Description: In financial transactions This domain indicates the identification code of the bank organization where the account is located in the network management transaction 800 / In 810, the domain contains code of the transaction initiator. Answer packets must be the same as the request packet. 18, BIT35 Diapass Data (TRACK 2 DATA) Bitmap Location: 35 Format: LLVAR Type: Z..37 Description: Written on the card diaphragm. The data composition follows ISO7811-1985 standards, and the data contains domain separators, but does not include card barators, end values, LRCs, etc. Whether the two magneur detection card is compliant with international standards. To support the international exchange receipt line, the separation of the secondary magnetic track should be changed to "=". In addition to any modification of the two-track data, such as modifying the check word, validity period, service code, etc. of the PAN. 19, BIT36 Triass Data (Track 3 DATA) Bitmap Location: 36 Format: LLLVAR Type: Z ... 104 Description: Written on the card three magnetrics. Data should be composed to follow the ISO4909 standard, including domain separators in the data, but does not include card barata, end, and LRC, etc. Note: The length will be described as a 3-digit number. 20, Bit37 Retrieve RETRIEVAL Reference Number Bitmap Location: 37 Format: Performance Type: AN12 Description: Retrieving Search 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽 聽聽The search index number does not require printing on the bill of cardholders. Its main purpose is to define a data item between the collection line and the authorization line to track and retrieve transactions. Authorization agencies can print search index marks on the customer's statement. The search index number is allocated by the collection line. Selection conditions: Can be included in the transaction request of the subscriber mechanism. If there is in the transaction request, it should be returned in response data. 21, BITHORIZATION Identification Bitmap Location: 38 Format: Type: AN6 Description: The returned code returned by the transaction authorization agency. The authorization code is used to authorize the credit card on the service point terminal; the authorization agency is selected by the network operation, and the present domain can be selected. 22, Bit39 Return Code (Response Code) Bitmap Location: 39 Format: Setting: AN2 Description: Define the encoding of its processing results to a transaction.
Return code is used to illustrate the processing status of the licensing authority to the financial (authorized) transaction; also to indicate the principal of the automatic key transaction; it is also used to indicate that the target host has received file modification, settlement, management, network management and other transaction requests. . The return code should be as accurate as possible, and the issues and status encountered should be described as much as possible. Network switched hosts, and collecting single line hosts may charge different transaction processing costs in different return codes, and perform different processing procedures. 23, BIT41 Care Card Terminal Location Location: 41 Format: Type: ANS8 Description: Defined to define a service terminal identification code in the subscriber unit, serve the terminal logo in the same merchant The code should be unique. 24, BIT42 Card ACEPTOR Identification Code Bitmap Location: 42 Format: Type: ANS15 Description: Defines the encoding of the trading unit (merchant) in the local and network. 25. Bit43 Card Acceptor Location Bitmap Location: 43 Format: Type: ANS40 Description: Country, province, province, province. City, etc. Selection conditions: If the external card network is used, you must include this domain. 26, Bit44 Additional Return Data (Additional ResponseData) Bitmap Location: 44 Format: LLVAR Type: ANS..25 Description: Other information returned by the authorization agency in the financial (authorized) transaction. 27, Bit48 Additional Data - Private Data-Private Bitmap Location: 48 Format: LLLVAR Type: ANS ... 999 Description: Bank Electronic Services System Use this domain to make the following use: Storage Batch query return data its format Corresponding to the output format: CURRENCY CODE, Transaction) Bitmap Location: 49 Format: Type: AN3 Description: Press ISO4217 Defined Trading Currency Code to indicate "Field04) Currency species. The transaction currency code refers to the trading type used by the transaction in the subscriber unit. 29, Bit50 settlement currency code (CURRENCY CODE, SETLEMENT) Bitmap Location: 50 Format: Settlement Type: An3 Description: Press ISO4217 The settlement currency code defined by ISO4217, used to represent settlement amount, settlement processing fee, settlement transaction fee, etc. Money species. The settlement currency code refers to the type of currency used during the settlement and liquidation process. 30, Bit52 User Password (PIN) Data (PIN DATA) Bitmap Location: 52 Format: Setting: B16 Description: The user is traded on the service terminal to identify some of the number of user legitimacy. PIN Press the ANSIX9.8 standard with the branch host key to form a ciphertext block. Selection conditions: This domain is required if the password is entered on the terminal.
31, BIT53 Password Related Control Information: 53 Format: Type: AN16 Description: This domain provides additional information about password blocks, used to point out for PIN Key for PIN, for Mac Calculated Mac Key. The domain format is shown in the table below: 0-1 Format code 2N "20" 2-3pin encryption algorithm 2N "01": DES 4-5 Cipheet block format 2N "01": ANSI 6PIN key index 1n'1 'or '2' 7MAC Key index 1n'1 'or' 2 '8-11MAC Check Data 4B 12-15 Filled 4N in the BOC credit card network PIN and MAC each use two keys ---' 1 'number and' 2 The 'key, the transaction calculates the PIN and MAC can only be used in one key, and the KEY index number used is required to fill in this domain. Conditions: If there is a PIN domain or MAC domain, you must have this domain. 32, Bit54 Additional Amount (Additional Amounts) Bitmap Location: 54 Format: LLLVAR Type: ANS ... 120 Description: This domain is returned by the authorized row host to the subscriber balance to the receipt terminal to display or print the order on. Up to 6 balances in this domain return, each balance return format is as follows: Location Description 0-1 Processing code 3-4 or 5-6-bit defined account type 2-3 amount type: 01- Account amount 02- Available amount 03- Has a amount of 04- Cut amount 40- Available withdrawal limit 56- The amount of money code 4-6 amounts of money code 7'd'-debit amount, 'C'-credit amount 8-19 balances Six The balance must be returned, and the available balance must be returned, and the available balance is displayed on the ATM, POS. 33, BIT64 Information Confirmation (MAC) bitmap position: 64 Format: Setting: B16 Description: The last domain of the packet is used to verify the source of information The legality, and whether the data in the packet is not tampered with. The calculation of the Mac is ANSIX.99, (the last eight-byte is not full of eight people left rosity, right-completed?) In order to improve efficiency, between the sender and the recipient, only the following important domains participate in the MAC computing . If there is the following data field in the packet, they will participate in the computation of the MAC. Bit Domain Name 2 Basic Account 3 Processing Code 4 Transaction Amount 11 System Tracking Number 12 Local Trading Time 13 Local Trading Date 32 Labor Code 38 Authorization Code 39 Return Code 41 Receive Terminal Code 49 Trading Many Code 95 Replacement Condition: Condition: Use only 1-64 domains of data to use this domain. 34, BIT70 Management Information Code Bitmap Location: 70 Format: Type: N3 Description: Used to define and maintain the internal communication network status of the bank electronic service system and the application work status. Network management information code is used to manage the date "Cutoff", "Sign On / Sign Off", "KEY Exchange", etc.
Supports the following network management information code NMIC network management information code action 001 check-in (SIGN ON) 002 Signing (Key Exchange) 201 Checkout Date Switch (CUTOFF) 202 Checkout Date Switch Complete 301 Test (Transaction Number) Bitmap Location: 74 Format: Type: N10 Description: Cyberbank software will receive the following one processing code Add the number of credit transactions. Trading code trading service 00 credit, shopping and service 01 credit, cash with 02 credit, adjustment (customer adjustment) 36, Bit75 credit automatic score transaction pen number (Credits, Reversal Number) bitmap location: 75 format: fixed Long Type: N10 Description: Loan Received Single Rights Automatic Raising, "Chargeback", etc. The total number of transactions such as Cyberbank software adds credit automatic transaction written transaction code trading services 20 credits when receiving the following processing code Return 21 credit, deposit 22 credit, adjustment (customer modification) 37, Bit76 debit transaction pen number (DEBITS, NUMBER) bitmap location: 76 Format: Type: N10 Description: Rebit of financial transactions The transaction number Cyberbank software increases the number of debit transactions when receiving the following processing code. Trading code transaction service 00 debit, shopping and service 01 debit, cash withdrawal 02 debit, adjustment (customer adjustment) 38, BIT77 debit automatic rush transaction pen number (Reversal Number) bitmap location: 77 format: fixed Long Type: N10 Description: Reserved Separates Automatic Raising, "Chargeback", etc. The total number of transactions such as Cyberbank software increases the number of debit reactive transactions when receiving the following, and reflected in the clearing book. Trading code trading service 20 debit (!!!), return 21 debit, deposit 22 debit, adjustment (customer revision) 39, Bit78 transfer transaction pen number (Number) bitmap location: 78 Format: Type of fixed length : N10 Description: The total number of transactions in the transfer. The system will increase the number of transfer transactions when receiving financial transactions such as processing code. Trading Code Transaction Service 40 Customer Related Account Transmission 40, Bit79 Transfer Automatic Raising Transaction Screen (Transfers, Reversal Number) Bitmap Location: 79 Format: Type: N10 Description: The total number of automatic transaction transactions. The system increasing the number of transfers automatic transactions when receiving an automatic transaction of the following processing code. Trading Code Transaction Services 40 Certificate of Transfers 41, Bit80 Query Transaction Writing Number (Inquiries, Number) Bitmap Location: 80 Format: Performance Type: N10 Description: Successful query trading number. The system software increases the number of query transactions when receiving the following processing code. Trading Code Trading Services 30 Query available 42, Bit81 Authorized Transaction Penmapped Location: 81 Format: Setting: N10 Description: Successful Authorized Transaction Total System Licensing Transactions When receiving an authorized transaction Pick up one.
43, BIT83 credit payment amount (Credits, Transaction FeEamount) Bitmap Location: 83 Format: Setting type: N12 Description: Net trading fee, such as the transaction amount is positive. 44, BIT85 Debit Transaction Amount (DEBITS, Transaction FeEamount) Bitmap Location: 85 Format: Performance Type: N12 Description: Net trading fee, such as the transaction amount is negative. 45, BIT86 credit transaction amount (Credits, Amount) bitmap location: 86 Format: Type: N16 Description: Loan the total transaction amount of financial transactions without any fees. The system increasing the credit transaction amount when receiving the following processing code and reflects in the clearing bill. Trading code trading service 20 credit, return 21 credit, deposit 22 credit, adjustment (customer modification) 46, Bit87 credit automatic ration amount (Credits, Reversal Amount) Bitmap location: 87 Format: Type: N16 Description: The total amount of credit card automatic transaction does not contain any fees. 47, BIT88 Debits, Amount) Bitmap Location: 88 Format: Type: N16 Description: Rebit of the total transaction amount of financial transactions, does not contain any fees. The system increasing the debit transaction amount when receiving the following processing code, and reflects in the clear bill. Trading code trading service 00 debit, shopping and service 01 debit, cash withdrawal 02 debit, adjustment (customer adjustment) 48, Bit89 debit automatic rush transaction amount (Reversal Amount) bitmap location: 89 format: fixed length Type: N16 Description: The total amount of the debit is automatically scored, does not contain any fees. 49, Bit90 Original Data Elements Bitmap Location: 90 Format: Type: N42 Description: Store some of the data for the original transaction, for modifying or automatic impartial. The data consists of the following five parts: Location Description 1-4 Information type code set to the original transaction information type code 5-10 System Tracking number former trading system Tracking number 11-20 Trading Date and time the trading date and time 21- 31 Original transaction of the original transaction of the original transaction is less than 11 institutional code, left supplement '0' 32-42 Original agency formerly transaction listing mechanism less than 11 institution code, left to make '0' 50, Bit91 file modified encoding (File Update Code) Bitmap Location: 91 Format: Type: AN1 Description: Use this domain to indicate how a file is maintained. Cyberbank supports the following modifications: 1 Add Record 2 Change Record 3 Delete Record 5 Query 7 Add File Selection Conditions: 51, Bit94 Service Indicator (Service Indicator) Bitmap Location: 94 Format: Type: AN7 Description: Indicator Modify the service.
Selection conditions: 52, Bit95 replacement amount (Replacement Amounts) Bitmap Location: 95 Format: Type: N42 !!! Description: Customer modification or part cancels the completed transaction, the last actual transaction amount, the original transaction of the transaction The amount is stored in 90 domains. Sub-elementamountAttribute transaction actual amount N12 settlement actual amount N12 actual transaction fee X N8 actual settlement fee X N8 53, Bit97 net settlement amount (NET settlement Amount) Bitmap location: 97 Format: Performance Type: x N16 Description: This domain is the net set amount. 502 transactions are used to send the net settlement amount of the day: "C0000000020000000", indicating the loan (' '?) 200,000.00 yuan. "D0000000020000000", indicating the debit ('-'?) 200,000 yuan. 54, Bit99 Settlement Identification Bitmap Location: 99 Format: LLVAR Type: N..11 Description: This domain stores a mechanism code for receiving liquidation information. Returns Packet This domain must be consistent with the request packet. 55, RECEIVING INSTITION Identification bitmap location: 100 format: LLVAR type: n..11 Description: Financial transaction This domain storage license agency code. Net management transactions, 800/820 transactions, this domain storage request destination mechanism code. Returns Packet This domain must be consistent with the request packet. 56, Bit101 File Name (FileName) Bitmap Location: 101 Format: LLVAR Type: ANS..17 Description: The file name set by the sender setting. 57, Bit102 Account 1 (Account Identification1) Bitmap Location: 102 Format: LLVAR Type: ANS..28 Description: A specific customer account. Account 1 is used to describe accounts affected by trading of debit, transfer, payment, etc. Selection conditions: Use when transferring. 58, Bit103 Account 2 (Account IdentiM) Bitmap Location: 103 Format: LLVAR Type: ANS..28 Description: Supplementary information of the transaction, such as the second currency, interest rate code, start date, etc. Definitions 000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 Position length Description 00-2122 Account 22-276 If this domain exists, press this institution code as routing information. Selection conditions: When the agency is transferred. 60, BIT123 New Pin Data Bitmap Location: 123 Format: LLLVAR Type: B ... 16 Description: Store new passwords when you change your password transaction. Format Reference 52 Domain Selection Condition: This domain must be available when you change your password transaction.
