Glossary

This reference defines the technical terms, abbreviations, and data formats used throughout the Getnet Pinpad Host-to-Host integration documentation.

General terms

The following terms define the primary components and message directions within the integration ecosystem:

Term	Definition
Host System	The proprietary system or cash register that initiates transaction requests and communicates with the Pinpad via the serial port. Also referred to locally as Caja or SP (Sistema Propio).
Pinpad (PP)	The Newland N750P physical terminal running the payment application.
Host Request	A formatted message generated and sent by the Host System to direct the Pinpad.
Pinpad Response	A formatted message returned by the Pinpad to convey status or data back to the Host System.
CTLSS	A contactless transaction performed using NFC technology.
CHIP	A contact transaction performed using the card’s EMV integrated circuit.
BANDA	A transaction performed via the card’s magnetic stripe interface.

Argentina Terminal ID Standard: Getnet uses an 8-digit alphanumeric code starting with “PP” to identify Points of Sale (PDV). This code is generated by Getnet and must be populated in the “ID del terminal” field for every transaction.

Encryption terms

The following terms describe the Pinpad encryption model. For the full scheme, see Pinpad Encryption.

Term	Definition
3DES DUKPT	Derived Unique Key Per Transaction with Triple DES. Encrypts the PIN/PINBLOCK and the PAN; never tracks.
RSA	Asymmetric encryption for messaging data: Track I, Track II, CVV, and EMV data; never the PIN or PAN.
PINBLOCK	The encrypted PIN block produced by DUKPT and returned in `Y19`/`Y02` responses.
PAN	Primary Account Number (card number). Returned DUKPT-encrypted as `ENC-PAN`; masked with zeros inside the tracks.
KSN	Key Serial Number for the DUKPT PIN key.
KSN-PAN	Key Serial Number for the DUKPT PAN key, with a counter independent of `KSN`.
ENC	Request field controlling PAN DUKPT encryption (`0` off, `1` on, `2` slot 3).
PMK	Master key position field. PIN PMK = value; PAN PMK = value + 1.
Key slot (3 / 4)	Secure DUKPT key positions. Slot 3 = PIN (and PAN if it is the only key); slot 4 = PAN.

Syntax and notation

Use the following notation rules when interpreting command structures and payloads:

Y0X.ABC: Refers to a specific field within a command.

[!NOTE] In this notation, Y0X is a placeholder where X represents the specific command ID (e.g., Y19, Y02, Y0Q). For example, Y0Q.QRD refers to the QRD field of the Y0Q command payload.

[Host]: Indicates a message payload originated by the Host System.
[Pinpad]: Indicates a message payload originated by the Pinpad.
// Comment: Double slashes indicate clarification text that is not part of the actual transmitted message.
SIN USO: Indicates a field included for legacy protocol compatibility (e.g., Lane3000). These fields do not contain relevant information for the Pinpad and typically use default values.

Data types and formatting

Command fields must adhere to these data type definitions and encoding rules:

Attribute	Description
A	Alphabetic character.
N	Numeric character.
AN	Alphanumeric character.
ANS	Alphanumeric and special characters.
H	Hexadecimal character.

Encoding representations

ASCII: Strings enclosed in quotes represent the ASCII representation of transmitted bytes. For example, “01a” represents the byte sequence 30 31 61.
Hexadecimal: Values ending with h represent raw hexadecimal bytes. For example, 1Ch indicates the byte value 1C.

The pages below put this nomenclature and notation to use:

Review Environment Setup to configure your Newland N750P terminal and Android Studio environment.
Follow the Connectivity Check guide to perform your first connection test using the Echo Request (Y0I) command.