Reprint
An overview of the Reprint message.
Overview
Please see below for information on configuring the rePrintRequest, as well as the expected rePrintResponse.
- rePrintRequest - originating from the application to initiate a request to reprint the last transaction or the transaction with a given orderCode
- rePrintResponse - originating from the card terminal to return the response of a reprint request
The Reprint request re-prints a physical receipt. To instead return receipt data in the response, please see the Get Last Receipt request
rePrintRequest
For a typical request the client must provide the following information:
| Field | Type | Length (chars) | Description | Example | Required | Card terminal support |
|---|---|---|---|---|---|---|
| msgLength | String | 4 | A 4-digit number padded with leading zeros indicating message length minus 4 (including any separators). The request will be rejected if the correct message length is not provided. | ‘0028’ | ✅ |  |
| sessionId | String | 6 | A unique number to control integrity of session sequence. | ‘002690’ | |
|
| msgType | String | 3 | ‘900’ | ‘900’ | ✅ | |
| orderCode | String | 16 | A 16-digit numeric string representing the order code | ‘1062160242000098’ | ✅ | |
The above information elements must be joined into one single string using ‘|’ as a separator. i.e.
0028|002690|900|1062160242000098
rePrintResponse
If the resulting string gets appropriately transmitted to the terminal, the terminal will respond with a rePrintResponse message 900.
A successful rePrintResponse looks as follows:
0014|002690|900|00
The table below summarises the contents of the response.
| Field | Length (chars) | Description | Example | Card terminal support |
|---|---|---|---|---|
| msgLength | 4 | A 4-digit number padded with leading zeros indicating the length of the message that follows (including separators). Before considering the msgLength value, please make sure that you've decoded the terminal response with UTF-8. | '0014' | |
| sessionId | 6 | A unique number to control integrity of session sequence. | '002690' | |
| msgType | 3 | '900' | '900' | |
| respCode | 2 | Approval status.00: success01: failed - out of paper02: failed - low battery03: failed - missing or incorrectly formatted orderCode04: no transactions found |
'00' | |
Get Support
If you would like to integrate with Viva, or if you have any queries about our products and solutions, please see our Contact & Support page to see how we can help!