> For the complete documentation index, see [llms.txt](https://testdocs.nibss-plc.com.ng/pos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://testdocs.nibss-plc.com.ng/pos/pos-interface-specifications-iso-8583-1987-version/data-element-definition-de39-de48.md). # Field Definition DE39 - DE48 #### **Field #39 - Response Code** | **Field No** | **Format** | **Attr** | | ------------ | ---------- | -------- | | **39** | | **an 2** | A code that defines the disposition of a transaction. | 00 | Approved or completed successfully | | -- | ---------------------------------------------------- | | 01 | Refer to card issuer | | 02 | Refer to card issuer, special condition | | 03 | Invalid merchant | | 04 | Pick-up card | | 05 | Do not honor | | 06 | Error | | 07 | Pick-up card, special condition | | 08 | Honor with identification | | 09 | Request in progress | | 10 | Approved, partial | | 11 | Approved, VIP | | 12 | Invalid transaction | | 13 | Invalid amount | | 14 | Invalid card number | | 15 | No such issuer | | 16 | Approved, update track 3 | | 17 | Customer cancellation | | 18 | Customer dispute | | 19 | Re-enter transaction | | 20 | Invalid response | | 21 | No action taken | | 22 | Suspected malfunction | | 23 | Unacceptable transaction fee | | 24 | File update not supported | | 25 | Unable to locate record | | 26 | Duplicate record | | 27 | File update edit error | | 28 | File update file locked | | 29 | File update failed | | 30 | Format error | | 31 | Bank not supported | | 32 | Completed partially | | 33 | Expired card, pick-up | | 34 | Suspected fraud, pick-up | | 35 | Contact acquirer, pick-up | | 36 | Restricted card, pick-up | | 37 | Call acquirer security, pick-up | | 38 | PIN tries exceeded, pick-up | | 39 | No credit account | | 40 | Function not supported | | 41 | Lost card | | 42 | No universal account | | 43 | Stolen card | | 44 | No investment account | | 51 | Not sufficient funds | | 52 | No check account | | 53 | No savings account | | 54 | Expired card | | 55 | Incorrect PIN | | 56 | No card record | | 57 | Transaction not permitted to cardholder | | 58 | Transaction not permitted on terminal | | 59 | Suspected fraud | | 60 | Contact acquirer | | 61 | Exceeds withdrawal limit | | 62 | Restricted card | | 63 | Security violation | | 64 | Original amount incorrect | | 65 | Exceeds withdrawal frequency | | 66 | Call acquirer security | | 67 | Hard capture | | 68 | Response received too late | | 75 | PIN tries exceeded | | 77 | Intervene, bank approval required | | 78 | Intervene, bank approval required for partial amount | | 90 | Cut-off in progress | | 91 | Issuer or switch inoperative | | 92 | Routing error | | 93 | Violation of law | | 94 | Duplicate transaction | | 95 | Reconcile error | | 96 | System malfunction | | 98 | Exceeds cash limit | #### **Field #40 - Service Restriction Code** | **Field No** | **Format** | **Attr** | | ------------ | ---------- | -------- | | **40** | | **N3** | An identification of geographic/service availability. Contains: · The area of usage and whether the card has additional read facilities | 1 | International card | | - | -------------------------------------------------- | | 2 | International card - integrated circuit facilities | | 5 | National use only | | 6 | National use only - integrated circuit facilities | | 9 | Test card - online authorization mandatory | · The authorization processing requirements for this card | 0 | Normal authorization | | - | ------------------------------ | | 2 | Online authorization mandatory | | 4 | Online authorization mandatory | · The range of services available and PIN requirements | 0 | PIN required | | - | ---------------------------------------------------------------------------- | | 1 | No restrictions - normal cardholder verification | | 2 | Goods and services only | | 3 | PIN required, ATM only | | 5 | PIN required, goods and services only at POS, cash at ATM | | 6 | PIN required if PIN pad present | | 7 | PIN required if PIN pad present, goods and services only at POS, cash at ATM | #### **Field #41 - Card Acceptor Terminal Identification** | **Field No** | **Format** | **Attr** | | ------------ | ---------- | --------- | | **41** | | **ans 8** | A unique code identifying a terminal at the card acceptor location. #### **Field #42 - Card Acceptor Identification Code** | **Field No** | **Format** | **Attr** | | ------------ | ---------- | ---------- | | **42** | | **ans 15** | A code identifying the card acceptor (typically a merchant). #### **Field #43 - Card Acceptor Name / Location** | **Field No** | **Format** | **Attr** | | ------------ | ---------- | ---------- | | **43** | | **ans 40** | The name and location of the card acceptor (such as a merchant or an ATM). This is a fixed length field consisting of 4 data elements: · The location information (positions 1 - 23), exclusive of city, state and country · The city (positions 24 - 36) in which the Point-of-Service is located · The state (positions 37 - 38) in which the Point-of-Service is located · The country (positions 39 - 40) in which the Point-of-Service is located #### **Field #44 - Additional Response Data** | **Field No** | **Format** | **Attr** | | ------------ | ---------- | ----------- | | **48** | **LLVAR** | **ans..25** | Used to provide other supplemental data (such as a telephone number for referrals) that may be required in response to an authorization or other type of transaction request. After a **PIN Change** request has been processed, this field contains the PIN offset (or PVV) in a 0610 message to the Source Node, as well as in a 0620 message to the Sink Node. If set in a 0610 message from the Sink Node, this field again indicates the PIN offset (or PVV). For **Visa Cash** load transactions, this field is used to carry signature information. In load responses, it contains the Visa Cash Service Identifier ("SV:") followed by the load response signature (S2). This is a fixed length field consisting of 2 data elements: · The Visa cash service identifier (positions 1 - 3), a constant value of "SV:" · The load authorization signature (positions 4 - 19) for this load operation In load settlement advices, it contains the Visa Cash Service Identifier ("SV:") followed by the load completion signature (S3). This is a fixed length field consisting of 2 data elements: · The Visa cash service identifier (positions 1 - 3), a constant value of "SV:" · The load completion signature (positions 4 - 19) for this load operation #### **Field #45 - Track 1 Data** | **Field No** | **Format** | **Attr** | | ------------ | ---------- | ----------- | | **48** | **LLVAR** | **ans..76** | The information encoded on Track 1 of the magnetic stripe as defined in ISO 7813, including field separators but excluding the begin sentinel, end sentinel and longitudinal redundancy check characters. Note that two structures are defined by ISO 7813, namely Structure A and Structure B. Structure A is reserved for proprietary use by card issuers, while Structure B is defined as follows: | **Field** | **Length** | | ------------------------ | ---------------------------------------------------------- | | Format Code | B (ASCII 66) | | Primary account number | up to 19 digits | | Field separator | 1 character (ASCII 61 or 94) | | Country Code | 3 digits (or a field separator if not present) | | Name | 2 to 26 characters (this field is further described below) | | Field separator | 1 character (ASCII 61 or 94) | | Expiry date (YYMM) | 4 digits (or a field separator if not present) | | Service restriction code | 3 digits (or a field separator if not present) | | Discretionary data | balance of available digits | The primary account number, expiry date and service restriction code fields are described in further detail under fields 2, 14 and 40 in this document. The structure of the **Name** field is defined in the following table. Sub-fields are separated by means of a space character (ASCII 32). The minimum encoded data allowed is a single character followed by the surname separator. | **Field** | **Notes** | | ---------------------- | -------------------------------- | | Surname | | | Surname separator | ASCII 47 | | First Name or Initial | | | Space | When required | | Middle Name or Initial | | | Period | When followed by Title; ASCII 46 | | Title | When used | The space character (ASCII 32) is required to separate the sub-fields of the **Name** field other than the surname. The separator terminating the surname should be encoded following the last sub-field of the **Name**field. If only the surname is encoded, it will follow the surname separator. #### **Field #48 - Additional Data** | **Field No** | **Format** | **Attr** | | ------------ | ---------- | ------------- | | **48** | **LLVAR** | **ans...999** | Used to provide linked account or mini-statement information for a linked account inquiry or a mini-statement inquiry. **Mini – statement Information** The format for field 48 when mini-statement data is to be sent downstream is as follows: 1\. A mini-statement heading line, containing tags to identify the format of the mini-statement data lines that follows, e.g. ``` DATE_TIME|SEQ_NR|TRAN_TYPE|TRAN_AMOUNT~ ``` The different fields of the mini-statement heading line are separated by bar characters ("|") and the line is terminated by a tilde character ("\~"). 2\. One or more mini-statement data lines, each similar to the identifying string above in structure, but containing the actual transaction data to be printed per line, e.g. ``` 19971201123123|001234|01|000000005000~ ``` Below is a list of tags supported. | **Field** | **Tag name** | **Format** | | ------------------ | ------------ | -------------------------------------------------- | | Sequence number | SEQ\_NR | n6 | | Date and time | DATE\_TIME | n14, CCYYMMDDhhmmss | | Terminal ID | TERM\_ID | n8 | | Transaction type | TRAN\_TYPE | n2 | | From account | FROM\_ACC | n2 | | To account | TO\_ACC | n2 | | Transaction amount | TRAN\_AMOUNT | n12 | | Account ID 1 | ACC\_ID1 | ans28 | | Account ID 2 | ACC\_ID2 | ans28 | | Authorization ID | AUTH\_ID | n6 | | Currency code | CURR\_CODE | n3 (Currency code of the Transaction Amount field) | | Surcharge | SURCHARGE | n8 | **Linked Account Inquiry** In the case of a linked account inquiry, this field contains information relating to the accounts linked to the card that initiated the transaction. The information for up to 20 accounts can be returned. Note that when "00" is specified as an account type in the original request, a list of all accounts linked to the card is retrieved, and not only the linked accounts of the default account type. The format of the information associated with each account is as follows: | **Field** | **Length** | **Description** | | -------------- | ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Account ID | 28 | The identifier uniquely identifying the account, left justified, space-filled. | | Account type | 2 | The ISO 8583 account type of the account. | | Currency code | 3 | The ISO numeric currency code of the account. | | Ledger balance | 13 | The ledger balance of the account. The first character contains the sign. A "D" indicates a debit (negative) balance and a "C" indicates a credit (positive) balance. |