Windcave iPP350 User manual

Version 2.3
Host Initiated Transactions

Page 2 of 27
Document Revision Information
Version Comments
0.1 Initial version.
0.2 Added Payline information.
0.3 Update to Document Formatting.
1.0 Release Version.
1.1 Signature support and Cancel transaction functionality.
1.2 Update to production endpoint address & transaction ow.
1.3 Removed DCC & Locate functions for now.
1.4 Added additional ReCo information & added Sandbox.
1.5 Added Paymark section updated images & xed typos. Updated Void and Refunds. Included
new conguration information.
1.6 Formatting changes.
1.7 Included cash out functionality.
1.8 Update to refund section and buttons.
1.9 Included multi-user testing.
2.0 Included additional ReCos and updated transaction completion response information.
2.1 Included Receipt transaction request.
2.2 Included Fail-Proof Result Notication functionality.
2.3 Rebranded Whole Document. Updated IWL250 documentation to Move5000 documentation -
Lorenzo Fernandez

Page 3 of 27
Copyright
© Copyright 2019, Windcave Ltd
33 Wilkinson Road,
PO Box 8400
Auckland 1060
New Zealand
www.windcave.com
All rights are reserved. No part of this work may be reproduced or copied in any form or by any means, electronic
or mechanical, including photocopying, without the express written permission of Windcave Limited.
Proprietary Notice
The information described in this document is proprietary and condential to Windcave. Any unauthorised use
of this material is expressly prohibited except as authorised by Windcave Limited in writing.

Page 4 of 27
Contents
1Introduction............................................................................................................................................................... 5
2Operation................................................................................................................................................................... 6
2.1 Endpoints & Firewall Considerations....................................................................................................................... 6
3Congurations .......................................................................................................................................................... 7
3.1 Direct external connection ....................................................................................................................................... 7
3.1.1 Direct external connection iPP350 .......................................................................................................................... 7
3.1.2 Direct external connection Move5000..................................................................................................................... 7
3.2 Connection to PC...................................................................................................................................................... 8
3.2.1 Connection to PC iPP350......................................................................................................................................... 8
3.2.2 Connection to PC Move5000 ................................................................................................................................... 8
3.3 IPP350 with MTM200............................................................................................................................................... 9
3.4 3G connection with Move5000 ................................................................................................................................ 9
3.5 Paymark key set up (NZ Only)................................................................................................................................ 10
3.6 Terminal conguration ........................................................................................................................................... 10
3.6.1 Initialisation............................................................................................................................................................. 10
3.6.2 Logon ...................................................................................................................................................................... 10
4Transaction Flow .................................................................................................................................................... 11
5Message Specication ........................................................................................................................................... 12
5.1 Transaction............................................................................................................................................................. 12
5.2 Status ...................................................................................................................................................................... 14
5.3 Buttons.................................................................................................................................................................... 17
5.4 Refunds ................................................................................................................................................................... 18
5.5 Receipt .................................................................................................................................................................... 19
6 Fail-Proof Result Notication (FPRN)………………………………………..……..…………………….……………………………………………………20
6.1 Fail-Proof Result Notication Transaction Flow…………………………………………………...……………………………………………………21
7Response Codes..................................................................................................................................................... 22
8TxnStatusId & StatusId........................................................................................................................................... 23
9 Parameters.............................................................................................................................................................. 24
10 Real-time Transaction Monitoring.......................................................................................................................... 26
11 Contact Windcave................................................................................................................................................... 27

Page 5 of 27
1 Introduction
The Windcave Host Initiated Transaction (HIT) solution is a web facing HTTPS service that permits control of a pay-
ment transaction on a Windcave terminal.
There is no requirement of a direct physical connection between the Point of Sale (POS) application and the
Windcave terminal. All required software is on the Windcave Terminal and Host. All messages are sent online via the
internet to create an end-to-end cloud-based payment solution.
The terminal can be connected online to a modem or router directly. However if required the HIT enabled terminal
can be connected to a POS’s PC as well to share the internet connection from the PC, in that case the POS’s PC
needs to have an SCR Controller software installed. For further details please refer to section 3 - Congurations.
The Windcave HIT sandbox is accessible online https://demo.windcave.com/SandboxPxHIT.aspx

Page 6 of 27
2 Operation
The POS initiates a transaction request to Windcave by sending an HTTPS POST request as an XML message to the
appropriate URL. See below section 2.1 (Endpoints & Firewall Considerations) for a list of URLs.
Windcave responds to the request, either immediately or after a congurable timeout period of a few seconds; after
receiving a response, the POS will continue to make Status requests until the Status response indicates that the
transaction is Complete (Complete value is returned as “1”) in Result.
Status responses from Windcave may contain instructions for the POS to permit information to be displayed for the
merchant (DL1, DL2) and enablement of buttons that may be used by the POS to interrupt the transaction or provide
feedback for example signature capture.
Note: For any new integrations, the POS must handle the entry of new users. POS applications are typically used by
many different customers.
As each customer has one or more HIT API users, a key part of POS development is ensuring that new user HIT
API credentials can be easily added into the POS and that the development credentials are not hard coded in any
way. Please ensure the API credentials conguration within the POS are also password protected or has some lev-
el of authorised access challenge.
2.1 Endpoints & Firewall Considerations
The POS can communicate with the Payment Host using HTTPS on the addresses below. Please ensure that your
network can accommodate this access.
Production: https://sec.windcave.com/pxmi3/pos.aspx
Test: https://uat.windcave.com/pxmi3/pos.aspx
The Windcave HIT terminal communicates with the Windcave Host using TCP on the addresses below. Please en-
sure that your network can accommodate this access.
Production: scr.windcave.com port 65
Test: uat.windcave.com port 65

Page 7 of 27
3 Congurations
3.1 Direct External Connection
Windcave HIT terminals can be congured to connect directly to an external Internet connection; this allows mer-
chants to remove all physical connection between their POS and the payment device; this option is available for both
the iPP350 and the Move5000.
No Windcave software is required on the PC running the POS. However only the Windcave key scheme is supported.
3.1.1 Direct External Connection iPP350
The iPP350 terminal is connected to an external network using three separate cables:
The customer must have a receipt printer and all receipt printing is controlled directly by the POS.
3.1.2 Direct External Connection Move5000
The Move5000 terminal is connected for online connectivity to an external network (via a router or modem) using a

Page 8 of 27
3.2 CONNECTION TO PC
Both the iPP350 and the iWL250 can be connected directly to the merchant’s POS. In order to run the HIT device, the
merchant must download the SCRController software from the Windcavewebsite.
Windcave and Paymark (NZ only) terminal key schemes are available.
3.2.1 Connection to PC iPP350
The iPP350 is connected directly to the POS using one USB-A cable:
The customer must have a receipt printer. The HIT response will contain the receipt content which is required to be
printed by the POS’s own receipt printer.
3.2.2 Connection to PC Move5000
The iWL25C terminal is connected directly to the POS using one USB-A cable. The device must also have power to
the base.
All printing is handled directly by the terminal’s on-board thermal printer.

Page 9 of 27
3.3 IPP350 with MTM300
The iPP350 can be connected directly to the MTM300. The MTM300 includes a thermal printer and allows both Pay-
mark and Windcave key schemes to be used. The MTM300/iPP350 connection requires two separate cables:
All printing is handled by the MTM300’s on-board thermal printer.
3.4 3G Connection with Move5000
The Move5000 accepts SIM cards which allows it to communicate using 3G. No cable connection is required other
than the standard power cable to the base.
Only Windcave keys can be used with this set up.
All printing is handled by the on-board thermal printer

Page 10 of 27
3.5 Paymark key set up (NZ Only)
Terminals using the Paymark key scheme must have their keys remotely injected before transacting. Please contact
our support team for assistance.
3.6 Terminal conguration
The Windcave terminal should come with precongured network settings. If there are any connectivity issues that
cannot be resolved, please contact Windcave Support staff.
3.6.1 Initialisation
Once powered up, the device will go through an automatic boot-up and online logon process. Once completed &
ready, PINpad will idle and display “EFTPOS” on the screen.
3.6.2 Logon
In order to prepare the terminal for processing transactions, the Logon message is used. A Logon uses the assigned
merchant number and terminal ID to login to the banking switch. This is recommended but optional as the terminal
will automatically log itself with the Windcave Host 10 seconds after connecting to the network. However if logon is
required please do the following manual logon process. Press the “Menu” button on the PINpad, and select “LOGON”.