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.
Syntax and Notation
Use the following notation rules when interpreting command structures and payloads:
- Y0X.ABC: Refers to a specific field within a command.
In this notation, Y0X is a placeholder where X represents the specific command ID (e.g.,Y19,Y02,Y0Q). For example,Y0Q.QRDrefers 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 sequence30 31 61. - Hexadecimal: Values ending with
hrepresent raw hexadecimal bytes. For example,1Chindicates the byte value1C.
Next Steps
Now that you are familiar with the system nomenclature and notation, proceed to the Getting Started section to prepare your environment:
- 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.