Getnet DocsGetnet Docs

Reprint Last Receipt

This guide shows you how to trigger a reprint of the last transaction voucher on the terminal. If a printer paper jam occurs or a customer requests an extra copy, you can reprint the last successful transaction without re-entering payment data.

Before you begin

Before reprinting a receipt, ensure you have:

  • The Getnet Payment App installed and active.
  • At least one transaction processed during the current session.

Send an Intent to the getnet://payment/v1/last-transaction URI. This deeplink automatically targets the most recent operation, so it needs no amount or NSU parameters.

getnet://payment/v1/last-transaction is the production URI. getnet://payment/v1/reprint is not a valid App2App deeplink in the payment scheme — do not use it.

The Reprint deeplink accepts the following optional parameters:

ParameterTypeRequiredDescription
allowPrintCurrentTransactionStringNoDefault "true". Set to "false" to receive the receipt data as automationSlip instead of printing on the terminal. See Printing Responsibility.
skipReceiptStringNo"true" does not print the client receipt; "false" (default) prints it. Rejected if allowPrintCurrentTransaction is "false".

Here’s how to trigger the reprint:

fun reprintLastVoucher() {
    val intent = Intent(Intent.ACTION_VIEW, Uri.parse("getnet://payment/v1/last-transaction"))
    intent.putExtra("allowPrintCurrentTransaction", "true")
    startActivity(intent)
}

Step 2: Verify the result

While the terminal handles the UI and printing, listen for the result to confirm the action was triggered. When allowPrintCurrentTransaction is "false", the response also returns the automationSlip receipt data.

ResultStatusMeaning
"0"SuccessThe reprint process started (or the receipt data was returned).
"3"ErrorNo previous transaction found to reprint.

If the last receipt was a report, no receipt is printed and a message is returned describing this scenario.

Next steps