Getnet DocsGetnet Docs

Printing Responsibility and Receipt Handling

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

Receipt generation and printing can be shared between the POS terminal and the automation system. This page describes how that responsibility is controlled and how receipt content is returned when the POS does not print.

What is printing responsibility

In an Integrated POS environment, the printing strategy is explicitly controlled by parameters sent with each operation (such as Sale or Refund). The terminal can either print receipts itself or return structured receipt content to the automation system, which may then print or store it. This allows flexible handling of receipts according to the partner’s business needs.

Printing strategies

Integrated POS supports two receipt handling strategies:

POS-Managed Printing

The terminal prints receipts directly using its built-in printer.

Automation-Managed Printing

The terminal returns structured receipt content to the automation system, which is responsible for printing or storing the receipt.

Both strategies always return an operation response to the automation system.

PrintOnPos parameter

The PrintOnPos parameter determines where the receipt is handled:

  • true — the POS prints the receipt.
  • false — the receipt content is returned in the response.

When PrintOnPos is false, the response includes a ReceiptContent object containing all receipt fields. For the full field list, see ReceiptContent Object.

ReceiptContent object

The ReceiptContent parameter is returned as a structured object containing all receipt lines generated by the POS.

This parameter allows the automation system to reproduce the receipt as generated by the POS, persist transaction records digitally, and print receipts using external printers.

When PrintOnPos is set to true, the ReceiptContent field may be empty or omitted in the operation response.

App printing responsibility

When the automation system manages printing, your app must print at least the merchant receipt. The merchant receipt provides the seller’s record of the transaction. Print the client receipt as well when the customer requires a copy.

Client and seller receipts

Depending on the operation and parameters provided:

  • Seller receipts may be printed automatically.
  • Client receipts may be printed or skipped (e.g. via SkipReceipt).
  • Receipt printing may be retried in case of paper issues.

Receipt behaviour is driven by operation parameters.

To see printing responsibility in action, explore these guides: