Request Parameters

This reference lists all public functions and parameters exposed by the Get Central / TpvpcImplantado middleware, using the exact parameter names and function signatures defined in the most recent Slim Pack documentation.
The tables below reflect the real invocation model used by the library. Parameters are listed exactly as they must appear in code, without aliases, translations, or inferred fields.

Initialization and Lifecycle Functions

These are the functions that are used to initialize and manage the middleware lifecycle.

fnDllIniTpvpcLatente

Initializes the middleware and opens communication with the PIN Pad. This function must be called once when the application starts.
Function signature (C#):
int fnDllIniTpvpcLatente(string cComercio, string cTerminal, string cClaveFirma, string cConfPuerto, string cVersion);
ParameterTypeRequiredDescription
cComercioStringYesMerchant identifier (FUC) provided by the acquiring entity.
cTerminalStringYesTerminal identifier assigned to the PIN Pad.
cClaveFirmaStringYesSignature key associated with the merchant and terminal.
cConfPuertoStringNoPort configuration. If empty or null, the value is loaded from local TPVPC configuration.
cVersionStringNoProtocol version ("5.1", "6.1", "8.1"). If empty, the configured default is used.
Return value: 0 if initialization succeeds. Any other value indicates a library-level error.

fnDllParaTpvpcLatente

Stops communication and releases all internal resources.

Function signature:
int fnDllParaTpvpcLatente();
This function has no input parameters.

Payment and Financial Operations

All financial operations are executed through exported functions that receive typed parameters and return an XML response buffer. A return value of 0 only indicates that the operation was processed; authorization must always be validated from the XML.

fnDllOperPinPad

Executes a PAGO or PREAUTORIZACION using a physical PIN Pad.
Function signature:
int fnDllOperPinPad(string cImporte, string cFactura, string cTipoOper, StringBuilder cXMLResp, int iTamMaxResp);
ParameterTypeRequiredDescription
cImporteStringYesAmount in format XXXXXXXXX.XX.
cFacturaStringYesMerchant operation reference.
cTipoOperStringYesOperation type: "PAGO" or "PREAUTORIZACION".
cXMLRespStringBufferYesOutput buffer that receives the XML response.
iTamMaxRespIntegerYesMaximum buffer size (recommended: at least 8192).

fnDllOperManualExt

Executes a PAGO or PREAUTORIZACION using manual card data entry.
Function signature:
int fnDllOperManualExt(string cTarjeta, string cCaducidad, string cCVC2, string cImporte, string cFactura, string cTipoOper, StringBuilder cXMLResp, int iTamMaxResp);
ParameterTypeRequiredDescription
cTarjetaStringYesCard number (15–19 digits).
cCaducidadStringYesExpiration date in AAMM format.
cCVC2StringConditionalSecurity code, required depending on merchant configuration.
cImporteStringYesAmount in format XXXXXXXXX.XX.
cFacturaStringYesMerchant operation reference.
cTipoOperStringYes"PAGO" or "PREAUTORIZACION".
cXMLRespStringBufferYesOutput XML buffer.
iTamMaxRespIntegerYesMaximum buffer size.

Confirmation and Refund Operations

These are the functions that are used to confirm and refund operations.

fnDllOperConfirmacion

Captures a previously authorized PREAUTORIZACION.
Function signature:
int fnDllOperConfirmacion(string cImporte, string cFactura, string cFacturaOriginal, StringBuilder cXMLResp, int iTamMaxResp);
ParameterTypeRequiredDescription
cImporteStringYesFinal amount to capture. Must be ≤ pre-authorized amount.
cFacturaStringYesNew reference for the confirmation.
cFacturaOriginalStringYesReference of the original pre-authorization.
cXMLRespStringBufferYesOutput XML buffer.
iTamMaxRespIntegerYesMaximum buffer size.

fnDllOperDevolucion

Executes a DEVOLUCION (refund) with or without original reference.
Function signature:
int fnDllOperDevolucion(string cImporte, string cFactura, string cFacturaOriginal, StringBuilder cXMLResp, int iTamMaxResp);
ParameterTypeRequiredDescription
cImporteStringYesRefund amount in XXXXXXXXX.XX format.
cFacturaStringYesNew refund reference.
cFacturaOriginalStringNoOriginal operation reference (required for referenced refunds).
cXMLRespStringBufferYesOutput XML buffer.
iTamMaxRespIntegerYesMaximum buffer size.

Recurring Payments

Recurring payments are performed using standard payment functions with additional parameters.

Primer pago recurrente

Executed via fnDllOperPinPad or fnDllOperManualExt with the following extra parameter:
ParameterTypeRequiredDescription
cSolicitudReferenciaStringYesMust be set to "S" to request generation of a recurring reference.

Pagos recurrentes posteriores

ParameterTypeRequiredDescription
cReferenciaStringYesReference returned during the first recurring payment.

Receipt Generation

These are the functions that are used to generate receipts.

fnDllGeneraRecibo

Generates receipts based on a completed operation.

Function signature:
int fnDllGeneraRecibo(string cXMLOperacion, string cTipoRecibo, StringBuilder cSalida, int iTamMaxResp);
ParameterTypeRequiredDescription
cXMLOperacionStringYesXML returned by the original operation.
cTipoReciboStringYes"CLIENTE" or "COMERCIO".
cSalidaStringBufferYesOutput buffer containing the generated receipt.
iTamMaxRespIntegerYesOutput buffer size.

Authorization Validation

All financial operations are considered AUTHORIZED only if the XML response contains:
xml
<estado>F</estado> <resultado>Autorizada</resultado>
Any other combination must be treated as DENIED, regardless of numeric codes or library return values.

On this page

Request Parameters