Getnet DocsGetnet Docs

Code Tables Reference

This document acts as a central repository for all standardized codes used as variables in Host System Requirements and Pinpad Responses. These identifiers are essential for parsing data, identifying errors, and configuring transaction behaviors.

Transaction type codes (TTY)

Defined in the [TTY] field during initialization (Y19). It dictates the financial nature of the operation.

CodeValueDescription
00PurchaseStandard purchase of goods or services.
01DebitStandard debit transaction.
02CreditStandard credit transaction.
09CashbackPurchase with cash withdrawal (Compra con Vuelto).
20RefundReversal or return of funds (Anulación/Devolución).

Account type codes (TDC)

Used in the [TDC] field of the Y15 command to suggest a target account type to the EMV kernel.

CodeValueDescription
NNot specifiedDefault value indicating no preference.
1Check AccountStandard checking account (Cuenta Corriente).
2Savings AccountStandard savings account (Cuenta de Ahorro).

Communication error codes (Y0E)

Returned by the Pinpad in the [COE] field of a Y0E response when a transaction fails or is interrupted.

CodeMessageCause / Meaning
01CANCELADOThe user pressed the red “Cancel” button or Host sent Y06.
02FALLA LECTURAChip/Stripe read failure or fallback restriction triggered.
03TARJETA INVÁLIDACard application not supported or card is blocked.
04ERROR EMVProtocol failure during the EMV Level 3 flow.
05ERROR PINSecure entry failed or was cancelled by the user.
06MONTO INVÁLIDOThe amount provided is malformed or exceeds maximum parameters.
07TIMEOUTThe user action or command wait time has expired.
08SIN LLAVESMissing DUKPT injection in Slot 3/4 or missing RSA keys.
99ERROR GRALUnhandled internal exception or general system fault.

Common EMV tags (CPG - TLV)

In a Y02 response, the [CPG] field contains a string of Tag-Length-Value (TLV) encoded data. These tags are critical for constructing authorization messages.

TagNameDescription
9F26Application CryptogramThe primary cryptogram (ARQC or TC) generated by the card.
9F10Issuer Application DataProprietary data required by the issuer for validation.
9F37Unpredictable NumberTerminal-generated random number for transaction uniqueness.
95Terminal Verification ResultsResults of offline validations performed by the terminal.
9BTransaction Status InfoIndicates the functions performed during the transaction flow.
9CTransaction TypeInternal EMV code (e.g., 00 for Goods, 09 for Cashback).

You will need a standard TLV parser on the Host System side to extract these specific values for your ISO 8583 authorization messages.

Mode of entry (MDI)

Identifies the physical hardware interface used to present the card.

CharacterModeHardware Interface
CChipEMV Contact Slot.
BBandaMagnetic Stripe Reader (Swipe).
LContactlessNFC Antenna (Tap).
MManualManually keyed card entry.
EErrorThe card could not be read.

PAN encryption control (ENC)

Set in the [ENC] field of Y19 and Y02 to control DUKPT encryption of the PAN.

CodeBehavior
0PAN DUKPT encryption disabled.
1PAN DUKPT encryption enabled.
2PAN encrypted using slot 3, with DUKPT enabled (forces single-key mode).

Master key position (PMK)

Set in the [PMK] field of Y19 and Y02. Only the PIN PMK is informed; the PAN PMK is always the PIN PMK plus one.

ValuePIN PMKPAN PMK
0–9The valueThe value + 1
N——

A value of N means no PIN is requested and no PMK is informed; the firmware defaults to slot 3 for the PIN and slot 4 for the PAN when a key is present. The default master key position (POSMK) is 3.

Key serial numbers (KSN)

DUKPT returns a Key Serial Number alongside each encrypted element.

FieldLengthDescription
KSN-PAN20 digits (10 bytes)KSN for the DUKPT-encrypted PAN.
KSN20 digits (10 bytes)KSN for the DUKPT PIN.

Key slots, independent counters, and PAN masking are explained in Pinpad Encryption.