> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/home/cloud-tsp-detokenization-api/data-elements-description.md). # Data Elements Description ## Message Data Elements Description This section provides detailed descriptions of all data elements used by the Cloud TSP / Remote Host interface messages. *** ### Field 02 – Primary Account Number | Attribute | `LLVAR; n..19` | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | The primary account number identifying a customer account. May be either the PAN value associated to the card issued by the Issuer, or the token value generated by the Cloud TSP during card digitalization. | *** ### Field 03 – Processing Code | Attribute | `n-6` | | ----------- | ------------------------------------------------------------------------------- | | Description | Code describing the impact of a transaction on the client and related accounts. | **Positions 1–2: Transaction Type Code** | Value | Description | | ----- | ----------------------------------- | | `00` | Purchases & Services | | `01` | Withdrawal | | `02` | Adjustment | | `09` | Purchase with cashback | | `11` | Quasi cash | | `12` | Manual cash | | `17` | Cash advance | | `19` | Fees | | `20` | Refunds | | `22` | Reversal | | `28` | MoneySend (MS) | | `31` | Balance request | | `36` | Cash balance inquiry | | `40` | Transfer request | | `52` | Credit – Return of goods | | `91` | Status Check | | `92` | Confirmation of a pre-authorization | | `93` | Card on File Token Processing | | `96` | Purchase at ATM | **Positions 3–4: Account Type (source)** | Value | Description | | ----- | ------------------- | | `00` | Not specified | | `10` | Savings account | | `20` | Checking account | | `30` | Credit card account | | `38` | Loan account | | `40` | Universal account | **Positions 5–6: Account Type (destination)** Same values as positions 3–4. *** ### Field 04 – Transaction Amount | Attribute | `n-12` | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | Transaction amount in local currency in the smallest unit associated to the currency (e.g. cents for Euro), right-justified with leading zeros. Example: `00 00 00 00 21 00` = 21 EUR. | *** ### Field 07 – Transaction Date and Time | Attribute | `n-10` | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | Transaction date and time, expressed in Coordinated Universal Time (UTC) or local time, at which the transaction takes place at the point of card acceptor location. Format: `MMDDhhmmss`. All transactions for a given domestic scheme or closed-loop environment must use the same convention (UTC or local). | *** ### Field 12 – Date and Time Local Transaction | Attribute | `n-14` | | ----------- | ---------------------------------------------------------------------------------------------- | | Description | Date and timestamp of the transaction at the card acceptor location. Format: `CCYYMMDDhhmmss`. | *** ### Field 14 – Expiration Date | Attribute | `n-4` | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | The expiration date of the payment product. May be either the expiration date of the card issued by the Issuer or the expiration date of the token generated by the Cloud TSP during card digitalization. | *** ### Field 18 – Merchant Type | Attribute | `n-4` | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Description | Classification of the merchant type of business or service. Allows the bank to identify the transaction type. Values must be compliant with ISO 18245. The following values are defined for Transit use cases: `4784`, `7523`, `4111`, `4131`, `4112`. | *** ### Field 19 – Acquiring Institution Country Code | Attribute | `n-3` | | ----------- | ---------------------------------------------------------------------------------------------------- | | Description | Code of the country where the acquiring institution is located. Refer to ISO 3166. Example: `02 53`. | *** ### Field 22 – POS Data | Attribute | `n-3` | | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | Description | Composed of two sub-fields: `n-2` (most significant digits) = PAN Entry Mode; `n-1` (least significant digit) = Terminal PIN Entry Mode. | **Field 01: PAN Entry Mode** | Value | Description | | ----- | ------------------------------------------------------------------------- | | `00` | Unknown | | `01` | PAN manual entry | | `02` | PAN read in Magnetic stripe | | `03` | PAN read in Magnetic stripe (fallback from chip) | | `04` | PAN read in QR code | | `05` | PAN read in contact chip | | `06` | PAN/Token entry via electronic commerce with optional AAV | | `07` | PAN read in contactless chip | | `08` | PAN/Token entry via electronic commerce containing cryptogram in field 55 | **Field 02: Terminal PIN Entry Mode** | Value | Description | | ----- | ------------------------------------------- | | `0` | Unknown | | `1` | Terminal has PIN entry capability | | `2` | Terminal does not have PIN entry capability | **Coding example:** `00 51` → Field 01 = `05` (contact chip), Field 02 = `1` (PIN capable) *** ### Field 23 – Card Sequence Number | Attribute | `n-3` | | ----------- | ---------------------------------------------------------------------------------------- | | Description | Allows distinguishing between separate cards related to the same primary account number. | *** ### Field 35 – Track2 Data | Attribute | `LLVAR ans...37` | | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | Track 2 data compliant with ISO 7813, excluding start/end sentinels and LRC. The PAN value may be either the PAN associated to the card or the token value. For chip transactions, DE 35 carries data read from the chip as EMV tag 57 (Track 2 Equivalent Data). The account number in DE 2 must match DE 35. | *** ### Field 37 – Retrieval Reference Number | Attribute | `an-12` | | ----------- | -------------------------------------------------------- | | Description | Unique reference used to retrieve the original messages. | *** ### Field 39 – Action/Response Code | Attribute | `n-3` | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | The code value must be part of the full successful/error code list below; otherwise an error is returned by TSP. TSP notifies TSH and the wallet in case of failed payment only for error codes listed below. | #### Behavior in 1120 Messages **a) Not a reversal or refund:** * Field 39 = `000` → Notification sent (result: APPROVED); 1130 response = `000` if no further error. * Field 39 in list (not `000`) → Notification sent (result: DECLINED); 1130 response = `000` if no further error. * Field 39 NOT in list → No notification; 1130 response = `006`. **b) Reversal (field 03 pos. 1–2 = `22`, field 39 = `000`):** * Notification: transactionType = PURCHASE, transactionResult = REFUNDED; 1130 = `000`. **c) Refund (field 03 pos. 1–2 = `20`, field 39 = `000`):** * Notification: transactionType = REFUND, transactionResult = APPROVED; 1130 = `000`. **d) Return of goods (field 03 pos. 1–2 = `52`, field 39 = `000`):** * Notification: transactionType = PURCHASE, transactionResult = REFUNDED; 1130 = `000`. **e) In 1110 and 1130:** corresponds to Cloud TSP message processing result. #### Error Codes | Code | Description | | ----- | ----------------------------------------------------------------------------------- | | `000` | Transaction or request approved | | `001` | Expired card | | `002` | Bad Merchant | | `003` | Unknown Card or wrong card status | | `004` | Terminal Transaction not permitted | | `005` | Cryptographic checks failure (wrong ARQC cryptogram) | | `006` | Message Format error | | `007` | Invalid amount | | `008` | Insufficient funds / over credit limit (token domain control) | | `009` | Duplicate transmission detected | | `010` | System error | | `011` | Lost card | | `012` | Stolen card | | `013` | Suspect fraud | | `014` | Cryptographic Key not supported | | `015` | Wrong Field 55 format | | `016` | Cryptogram expired (specific to QR Code project) | | `017` | Amount in message field not within allowable limits derived from amount in field 55 | | `018` | Currency code in message field does not match currency code in field 55 | | `019` | Local Verification Results check failed (Apple Pay) | | `020` | Required CDCVM stamp is missing | | `021` | CDCVM Stamp checking failure | | `024` | RFU – Required Cloud PIN stamp is missing | | `025` | RFU – Cloud PIN stamp checking failure | | `029` | Cloud PIN not supported | | `030` | ATC Check failure | *** ### Field 42 – Card Acceptor Identification Code | Attribute | `ans-15` | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | Identifies the point of the transaction in both local and interchange environments. Used as merchant ID in POS transactions. Left-justified with spaces on right positions. | *** ### Field 43 – Card Acceptor Name and Address | Attribute | `ans-55` | | ----------- | ------------------------- | | Description | Composed of 7 sub-fields: | | # | Attributes | Description | | - | ---------- | ----------------------------------------- | | 1 | `ans-22` | Card Acceptor Name | | 2 | `ans-1` | Separator: `'/'` | | 3 | `ans-5` | Card Acceptor ZIP code | | 4 | `ans-1` | Separator: `'/'` | | 5 | `ans-22` | Card Acceptor Location City | | 6 | `ans-1` | Separator: `'/'` | | 7 | `ans-3` | Card Acceptor State/Province/Country Code | *** ### Field 48 – Additional Data, Private | Attribute | `LLLVAR ans...255` | | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | Dedicated to the storage of additional data. Composed of concatenated sub-fields, each with: Sub-field Identifier (3 chars) + Sub-field Length (3 chars) + Sub-field Value. | | Identifier | Length | Value | Presence | | ---------- | -------- | ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------- | | `001` | `002` | Encrypted key index (hex `0–9`, `A–F`). Must be unique per processor. | Required when field 64 is present | | `002` | `032` | MAC key: 32 hex characters representing 16 bytes of MAC key encrypted under the key at the given index. | Required when field 64 is present | | `003` | `003` | CVV2 value (3 digits) | Currently not used | | `004` | `032` | AAV | Currently not used | | `005` | up to 32 | Archive Reference (up to 32 alphanumeric chars) | Conditional in 1110/1130 – depending on project requirements (recurring payment) | | `006` | `001` | Transaction Category Code (TCC) — see values below | Required for transit transactions; optional otherwise | | `007` | variable | Acquirer Institution ID from request | Conditional in 1110/1130 – depending on project requirements | **TCC Values (identifier `006`):** | Value | Description | | ----- | ------------------------------------ | | `A` | Car rental | | `H` | Hotel | | `R` | Retail sale | | `M` | MOTO (mail order or telephone order) | | `X` | Public transport services | **Coding example:** ``` ASCII: 001 002 01 002 032 244726D701906C085F977A94166C55F3 005 012 11AA22BB33CC ``` *** ### Field 49 – Transaction Currency Code | Attribute | `n-3` | | ----------- | -------------------------------- | | Description | Local transaction currency code. | *** ### Field 55 – Chip Related Data | Attribute | `LLLVAR b...255` | | ----------- | ------------------------------------------------------------------------------------------------- | | Description | Contains data related to ICC systems. BER-TLV structured as defined in EMV specifications Book 3. | **Mandatory data elements in field 55 (when present in 1100 message):** | Tag | Length | Data Element | | ------ | ----------------- | ------------------------------------------------ | | `5F2A` | 2 | Transaction Currency Code | | `82` | 2 | Application Interchange Profile | | `95` | 5 | Terminal Verification Result | | `9A` | 3 | Transaction Date | | `9C` | 1 | Transaction Type | | `9F02` | 6 | Authorized Amount | | `9F03` | 6 | Other Amount (default `000000000000` if ignored) | | `9F10` | variable up to 32 | Issuer Application Data | | `9F1A` | 2 | Terminal Country Code | | `9F26` | 8 | Application Cryptogram | | `9F27` | 1 | Cryptogram Information Data | | `9F36` | 2 | Application Transaction Counter | | `9F37` | 4 | Unpredictable Number | **Data elements in field 55 (when present in 1130 message):** | Tag | Length | Data Element | | ---- | ----------------- | ------------------------------------------------------- | | `91` | variable up to 16 | Issuer Authentication Data (containing ARPC cryptogram) | > Field 55 is present in 1130 only when PAN Entry Mode = `04` (contact chip). **Example:** ``` 69 9f 02 06 00 00 00 00 21 00 9f 03 06 00 00 00 00 00 00 9f 1a 02 02 50 95 05 00 00 00 00 00 5f 2a 02 09 78 9a 03 18 01 09 9c 01 00 9f 37 04 0f 01 0e 03 82 02 1a 80 9f 36 02 00 01 9f 10 20 0f a5 01 a0 81 01 00 00 ee af 28 c6 83 81 c2 ed 0f 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 9f 26 08 a1 a7 17 06 5f f0 30 a3 ``` Length: `69` hex = 105 dec *** ### Field 56 – Token Related Data | Attribute | `LLLVAR b...255` | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | Token-related data. BER-TLV structured as defined in EMV specifications Book 3. When no token-related data has to be communicated, the field is absent. | | Tag | Max Length | Type | Messages | Data Element | | ---- | ---------- | ---- | --------- | ------------------------------------------------------------------------------------------------------------------ | | `05` | 19 | `n` | 1110/1130 | Token value (from DE02 of corresponding 1100/1120) | | `06` | 32 | `an` | 1110/1130 | Wallet Provider ID (e.g. `APPLE_PAY`, `SPAYHCE`, `ANDROID_PAY`) | | `07` | 32 | `an` | 1110/1130 | Device Brand (e.g. `Samsung`) | | `08` | 32 | `an` | 1110/1130 | Device Model (e.g. `SM920T`) | | `09` | 11 | `n` | 1110/1130 | Token Requestor ID | | `10` | 16 | `an` | 1110/1130 | Device type (e.g. `MOBILE_PHONE`, `TABLET`, `WATCH`, `COMPUTER`, `HOUSEHOLD`, `WEARABLE`, `AUTOMOTIVE`, `UNKNOWN`) | | `11` | 4 | `an` | 1110/1130 | Token type (e.g. `SE`, `HCE`, `TEE`, `COF`) | | `12` | 11 | `n` | 1110/1130 | Alternative Token Requestor ID (for applicable projects) | > The list of data included by the TSP in each response (1110/1130) is defined per project during the specification phase. *** ### Field 64 – Message Authentication Code | Attribute | `b-8` | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Description | Message Authentication Code (MAC) validates the source and text of the message between sender and receiver. Generated using the MAC key provided in field 48 (identifier `001`). See MAC Details. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.payments.thalescloud.io/home/cloud-tsp-detokenization-api/data-elements-description.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.