Terminal protocol Tatrabank Closure Connector
[ | version 3.0]
You are viewing outdated version, see the latest version
Connector
The connector is forbidden for use by the platform background agent.
Connector processing type: Row by row!
Using the Connector for Closure within the Tatrabank protocol serves two main purposes:
Firstly, it signifies the closure of the accounting period, often accompanied by operational transitions like changes of operators.
Secondly, it undertakes the critical task of verifying the transactional balance between the payment terminal (or cash register) and the authorization system. This transactional verification process ensures the integrity of financial records and compliance with regulatory standards, contributing to operational efficiency and transparency.
Configuration
POS Connection
IP Address
Destination IP address of terminal (e.g. 10.0.0.5)
IP Port
Destination port of terminal (e.g. 2050)
POS Settings
Protocol version
Version of ECR protocol (e.g., 1.00)
ECR info data
ECR integrator specific data sent by the cash register (e.g., IGS)
Currency Code
Currency code used in transaction (e.g., 978 for Euro)
Print on POS flag
Print the receipt on the terminal (e.g., 0 or 1)
Send formatted receipt flag
Send the receipt to ECR (e.g., 0 or 1)
Input & Output Schema
Input
Data schema is optional
The connector does not expect a specific schema. The required data structure can be achieved by correct configuration. Although the selected connector doesn't require a schema generally, the individual integration task step may need to match the output data structure of the preceding task step and use a data schema selected from the repository or create a new input schema.
Output
Pos Tatrabank Closure Output Schema (1.0.0)
| Column | Data type | Allow null | Description |
|---|---|---|---|
| Totals | JSON | Yes | Terminal and server-side totals/subtotals. Totals record in JSON structure - see below |
| IsTransactionApproved | Bool | No | Flag identifies that the transaction has been approved |
| EcrVersion | String | Yes | Version of ECR protocol (e.g., 1.00) |
| ReceiptEncoding | String | Yes | Encoding of receipt data. Possible encodings are UTF-8 (default), ASCII, CP1250 and ISO-8859-2 |
| ResponseCode | String | Yes | Alphanumeric response code from host |
| ResponseCodeDescription | String | Yes | Response code description from host. Text is encoded using the same encoding scheme as specified in field “e” |
| LocalTextResponse | String | Yes | Description of locally declined transaction |
| CustomerReceipt | String | Yes | Formatted customer receipt data for ECR printer |
| MerchantReceipt | String | Yes | Formatted customer receipt data for ECR printer |
Totals record in JSON structure:
-
DebitCount - Number of debit transactions (Sales)
-
DebitAmount - Total amount of debit transactions
-
CreditCount - Number of credit transactions (Refunds)
-
CreditAmount - Total amount of credit transactions
Release notes
3.0.0
- First release