Getnet DocsGetnet Docs

Generate and Print Receipts

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

Every financial operation processed by Get Central may result in the generation of one or more receipts, depending on the operation type, terminal configuration, and certification rules. Receipt handling is largely managed by the TPVPC itself and is subject to strict technical and regulatory constraints.

This guide applies to Slim Pack.

Get Central supports two receipt-handling models:

  • Automatic receipt generation and printing, fully managed by the TPVPC
  • Manual receipt handling, by reading receipt-related fields from the XML response

Requirements

Before working with receipts, ensure that:

  • A transaction has completed and returned a final XML response
  • The host machine has a default printer correctly configured
  • The printer type (ticket printer or A4) matches the terminal certification

Receipt layout, content, and printing behavior are controlled by the TPVPC. The client application cannot alter certified receipt formats.

Receipt Generation Process

Receipt handling depends on the operating mode and terminal configuration.

Step 1: Automatic Receipt Generation (TPVPC-Controlled)

In the Slim Pack model, receipts are generated and printed automatically by the TPVPC after a successful operation (PAGO, DEVOLUCION, CONFIRMACION, etc.).

Key characteristics:

  • The application does not call a receipt-generation function
  • Receipt content is derived from the transaction result
  • Printing is sent to the system default printer
  • The application cannot suppress, customize, or reformat the receipt

Depending on the operation and configuration, the TPVPC may print:

  • Customer receipt
  • Merchant receipt
  • Both receipts

Step 2: Receipt Data in the XML Response

Even when printing is automatic, the XML response returned by Get Central may include receipt-related elements that can be used for:

  • On-screen display
  • Storage for audit purposes
  • Reprinting logic (if supported by the environment)

Common receipt-related elements include:

Data ElementXML TagDescription
Receipt lines<linea>Individual formatted receipt lines
Customer-only receipt<ReciboSoloCliente>Indicates customer-only receipt flow
Masked card number<tarjetaClienteRecibo>Masked PAN suitable for printing
Terminal identifier<terminal>Terminal that processed the operation
Date and time<fechaOperacion>Operation timestamp

The presence of receipt-related tags depends on the operation type and terminal behavior.

Step 3: Manual Receipt Construction (Limited Use)

Manual receipt construction is not the primary model in Slim Pack integrations. It may only be considered when:

  • The integration environment explicitly disables automatic printing, or
  • The receipt is required for non-print purposes (screen display, archival storage)

In this case, the application must extract receipt-safe fields from the XML response.

At minimum, a receipt must include:

Required FieldXML Tag
Authorization result<resultado>
Response code<codigoRespuesta>
Amount<importe>
Currency<moneda>
Date and time<fechaOperacion>
Masked card<tarjetaClienteRecibo>
Terminal<terminal>

Security rule: Full PAN, CVV, PIN, or cryptographic data must never be printed or stored. Only masked values returned by the TPVPC may be used.

Step 4: Compliance and Retention

Regardless of the receipt strategy:

  • Receipts must only be issued after a transaction is AUTHORIZED
  • Stored receipts must match the final transaction result
  • Retention policies must follow local fiscal and accounting regulations