Windcave iPP350 - Fail-Proof Result Notification (FPRN)

Page 20 of 27
6 Fail-Proof Result Notication (FPRN)
Fail-proof result notication (FPRN) is a service that provides additional assurance that the merchant website will
receive notication regarding the outcome of transactions completed via the Windcave host. This service allows
merchant POS to stop checking for the status stage after the transaction is initiated and simply indicate nalization
of the transaction.
FPRN can be enabled by adding <UrlSuccess> and <UrlFail> parameters in the request. Notication will be sent by
Windcave host once the transaction is nalised. Windcave host will only send FPRN notication when the response
result of TxnStatusId is 7 – Verifying Signature and 8 – Display Result. However, it is recommended displaying a user
-friendly prompt such as “Transaction in progress—Please refer to terminal” on the screen of POS. The only case that
the POS would still have to display prompts/buttons is when the terminal must require user selection (TxnStatusId =
7) for approving signature with mandatory button options ‘YES’ and ‘NO’.
As soon as the response result of TxnStatusId is 7 or 8, a background process at Windcave makes an HTTP GET re-
quest to the merchant-nominated success or failure URL. If the merchant web site is unreachable or returns any
HTTP status code other than 200, 201, 302, 303, 404 or 502 the HTTP GET is retried up to a maximum of six times. It
will give up immediately on receiving a 404 (page not found) HTTP status code or 502 (Bad Gateway) HTTP status
code. A 500 HTTP status code, indicating a temporary problem at the client site, will cause a retry.
Please note that merchant POS would still have to perform the status request after the transaction is initiated if they
want to update prompts for every stage on the screen of POS.
To ensure that the web application is in the best position to acknowledge the outcome of every transaction, certain
guidelines should be followed.
The merchant web application should not;
 Filter or base any conditional logic upon the originating IP address (this can vary)
 Depend upon receiving one and only one request for the success/fail URL from the Windcave FPRN system
(multiple requests may be sent).
N.B. The URL at which the merchant website will process FPRN requests must be exposed via standard inter-
net ports i.e. port 80 or port 443 for SSL/TLS trac. When specifying UrlSuccess and UrlFail values do not
specify a non-standard port number within the URL.
Example Transaction Request with FPRN:
<Scr action="doScrHIT" user="xxx" key="yyy">
<Amount>1.05</Amount>
<Cur>NZD</Cur>
<TxnType>Purchase</TxnType>
<Station>1234567890</Station>
<TxnRef>123</TxnRef>
<DeviceId>Device 1</DeviceId>
<PosName>POS 1</PosName>
<PosVersion>Pos V1</PosVersion>
<VendorId>PXVendor</VendorId>
<MRef>My Reference</MRef>
<UrlSuccess>https://webhook.site/d85dd2b9-c1c0-4a5f-8109-bcf8b22eaab6??txnRef=12345&station=1234567890</
UrlSuccess>
<UrlFail>https://webhook.site/d85dd2b9-c1c0-4a5f-8109-bcf8b22eaab6?txnRef=12345&station=1234567890</UrlFail>
</Scr>