Getnet DocsGetnet Docs

Protocol and Type Reference

The Get Mini framework defines a series of Data Transfer Objects (DTOs) and protocols to manage merchant context, hardware initialization, and transaction results.

Configuration & Merchant DTOs

These types are used to establish the identity and environment of the merchant.

CommonUtils (Environment Setup)

Environment configuration is handled via global methods rather than a configuration object.

IdentifierDescription
"des"Development environment
"int"Integration/Testing environment
"ccal"Certification environment
"real"Production environment

MerchanDTO

Required to link a physical PIN pad to a merchant account during initialization.

PropertyTypeDescription
fucString9-digit merchant code
terminalStringTerminal number (e.g., “1”)
claveComercioStringMerchant security key
nombreComercioStringName displayed to the user

Protocol Definitions

Implement these protocols in your delegates to receive SDK callbacks.

RedsysBTPinpadPaymentDelegate

Handles the lifecycle of a payment transaction and real-time user feedback.

MethodWhen CalledParameters
onPaymentProcessState changes in the PIN padid (Result), NSError
onPaymentFeedbackReal-time choice required (DCC/Installments)RespuestaTransaccionDTO, NSError
onPaymentFinishedTransaction completes (Approved/Denied)RespuestaTransaccionDTO, NSError

RedsysBTPinpadInitDelegate

Monitors the connection and key-injection process of a PIN pad.

MethodWhen CalledParameters
onInitProcessStatus update during Setupid (Status string)
onInitFinishedSetup completePinpadConfig, NSError

Transaction Data Types

PagoDTO

Defines the parameters for a specific payment attempt.

PropertyTypeDescription
valorCompraIntAmount in cents (e.g., 1050 for 10.50€)
monedaIntISO 4217 code (e.g., 978 for EUR)
tipoOperString“Autorización” or “Preautorización”
emailClienteString(Optional) Triggers automatic receipt email
tlfClienteString(Optional) Triggers automatic receipt SMS

RespuestaTransaccionDTO

The primary result object returned after a transaction attempt.

PropertyTypeDescription
estadoString“F” (Finalized), “G” (Denied), “T” (Technical Error)
resultadoString“Autorizada” or “Denegada”
identificadorRTSString24-char unique key for refunds and queries
literalesArrayArray of strings required for the receipt
autenticadoPorPinBoolIndicates if a physical signature is required
tokenString(Pay by Reference) Card token for recurring payments

Inquiry & Management DTOs

OperacionDTO

Represents a past transaction retrieved via the history query.

PropertyTypeDescription
importeStringFormatted amount (e.g., “10.50”)
fechaOperacionNSDateTimestamp of the transaction
numAutorizacionStringGateway authorization code
facturaStringYour internal invoice/order ID

PerfilComercioRespuesta

Returned by peticionPerfilComercio to check active terminal features.

PropertyTypeDescription
permitePreautoBoolMerchant can perform Pre-authorizations
permiteDCCBoolMerchant can handle installments/currency conversion
permiteEntradaManualBoolMerchant can type card numbers manually

Enumerations

PinpadTechnology

Specifies the communication protocol for the hardware.

ValueDescription
pinpadBluetoothStandard Bluetooth connection (Most devices)
pinpadBluetoothPanBluetooth Personal Area Network (FlyPOS devices)
pinpadBluetoothSMPPSecure Bluetooth communication

| pinpadWifi | Connection via local network/Wi-Fi |

Implementation Notes

  1. Amount Formats: Always check if a method expects cents (Int) or formatted strings (String). Payments usually use cents; refunds use strings.
  2. Result Codes: A code of 117 in error.code specifically indicates a “Wrong PIN” denial.
  3. Data Persistency: The SDK uses local SQLite storage for certain modules; ensure you include the -lsqlite3 linker flag.