Skip to content
background-image background-image

Terminal protocol Tatrabank Refund 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!

The connector that helps connect external cash register systems (ECR) and a payment terminal when processing refunds from a merchant's account to a cardholder's account. The connector can convert requests from cash register systems entered in a user-friendly format (e.g., CZK 100) into a format the payment terminal understands. Subsequently, it can transform the transaction processing results returned by the terminal into a format comprehensible to the POS system.

Transfer of an amount from the account of the merchant to the cardholder’s account. This transaction is very risky for fraud, so please handle it carefully.


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 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


search: exclude: true


Pos Tatrabank Refund Input Schema (1.0.0)

Column Data type Allow null Description
Amount Double No Transaction amount defines the value of a transaction. The amount is given without decimal point. Example: the amount "2000" is given for the amount 2000 HUF or 20,00 CZK
Transaction Id String Yes Alphanumeric identification used for transaction identification
CardNumber String Yes Track2 record if magstripe was read by ECR
TerminalId String Yes Terminal logical identifier on which the transaction will be made

Output

Pos Tatrabank Refund Output Schema (1.0.0)

Column Data type Allow null Description
IsTransactionApproved Bool No Flag identifies that the transaction has been approved
PrimaryAccountNumber String Yes PAN and expiry date of card separated by “=” character. Some parts of card number should be masked by “*” character
TerminalId String Yes Terminal logical identifier on which the transaction will be made
AuthorizationCode String Yes Field value depends on card brand and issuer AC. The only permitted special symbol is „ “ (space ASCII 0x20).
PinIndicator String Yes Cardholder verification method. Possible values are: Y – PIN, N – None, S - Signature
CardType String Yes Alphanumeric string which identifies the type of card (see Supported card brands)
ResponseCode String Yes Alphanumeric response code from host
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
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
HashCard String Yes PAN hashed with SHA1 function
ApplicationId String Yes Application identifier
AuthorizedAmount Double Yes Amount that was authorized by the AC
Amount Double No Total transaction amount
TransactionTimestamp DateTime Yes Timestamp of transaction in format: yyyy-mm-dd HH:MM:SS
DedicatedFileName String Yes Dedicated File Name (EMV Tag: 84)
ApplicationLabel String Yes Application Label (EMV Tag: 50) + ‚contactless‘ (if applicable)
VariableSymbol String Yes Unique transaction identification generated by ECR for matching transaction in accounting
CustomerReceipt String Yes Formatted customer receipt data for ECR printer
MerchantReceipt String Yes Formatted customer receipt data for ECR printer

Release notes

3.0.0

  • First release