Windcave iPP350 - Page 15

Page 15 of 27
Please Note: It is important that the POS integration continues to request a status check until after the
POS user appropriately handles the prompt on the POS and/or terminal and the nal response contains
the Complete tag value as 1. The HIT interface allows only one transaction to be fully completed at a time.
A pending transaction completion will result in an “Existing Txn In Progress” error. This should be handled
by sending the Status request for the TxnRef of the transaction until it reaches the Complete stage.
5.2.2.3 Final Status Response on completion of Transaction
On completion of a transaction the Complete XML element will be set to 1. The result of the transaction will be popu-
lated inside the Result XML element. Below property elements are contained in the transaction response and Result
XML element.
Property Description
TxnType Transaction Type. Normally the HIT transaction response’s TxnType value is as Status.
TxnRef TxnRef value for the original request and transaction.
StatusId Status of the current request Refer to the section TxnStatusId and StatusId for more infor-
mation.
TxnStatusId Status ID related to current transaction.
Complete If transaction is completed this eld will be set to 1.
RcptW Receipt Width species the maximum character limit per receipt content’s line. A terminal’s
account is setup with a default receipt width character length. The xed character limit can
be used to center justify the receipt content per line to get the standard receipt format.
Rcpt Actual EFTPOS receipt content that should be physically printed in case the POS handles
the EFTPOS receipt printing. All receipt content should be printed to ensure nancial data
integrity.
Result Encloses the nal transaction results with specic transaction data elds.
AC AuthCode. Up to 6 character authorisation code.
AP Approved ag. “1” indicated approved (funds transfer or reserve); “0” indicated declined or
not approved.
CN Masked Card Number.
Complete 1 indicates transaction session is completed. The POS should stop sending status requests
CT Card Name e.g. Visa.
DS Expected Settlement Date of Transaction. Format is yyyymmddhhmmss.
DS_TZ TimeZone applied to the DS value.
DT Date of Transaction. Returned in Timezone Format is yyyymmddhhmmss.
DT_TZ TimeZone applied to DT value.
PIX EMV specic data.
RID EMV specic data .
RRN Retrieval reference Number
ST STAN. The System Trace Audit Number which identies the transaction number processed
through the merchant account.
TR DpsTxnRef. Unique global transaction identier generated by Windcave and returned for
every transaction. This value can be provided to support teams to identify transactions.
DBID DpsBillingId is a card token generated by Windcave. Token used to rebill the card for sub-
scription or recurring based payments. Rebilling requests are sent via the PxPost or Web-
service API.
RC Response Code. See section 6 Response Codes
RT Response Text. See section 6 Response Codes.
RTT Round Trip Time in Milliseconds –provides an indication of network health (between
Windcave and Windcave Terminal).
AmtA Amount value of the transaction in cents.