Windcave iPP350 - Refund Procedures

To Next Page

To Previous Page

Page 18 of 27

5.4 Refunds

5.4.1 Matched refunds initiated via HIT request

To initiate a refund directly from the POS, the DpsTxnRef of the initial transaction must be included. The unique TxnRef

is used separately as a reference to the refund and must be unique.

5.4.2 Unmatched refunds with refund card

To initiate a refund directly from the POS and authorise with a merchant refund card, the following example XML should

be modied and sent. The DpsTxnRef tag does not need to be included, instead for authorization the terminal will

prompt for the merchant’s refund card to be swiped and PIN entered before the customer presents their card for the

refund. The merchant refund card is setup by Windcave. For extra security, it is expected the POS requires own authori-

zation before requesting unmatched refund via the POS.

5.4.3 Matched refunds via ecommerce solution

The PxPost or Web Service eCommerce API can be used to process refunds with the matched DpsTxnRef of the given

HIT transaction. For more information on PxPost and Web Service, please visit our website

https://www.windcave.com/developer-e-commerce-merchant-hosted-transaction-processing

When using PxPost or Web Service to handle refunds, the HIT user and the eCommerce API user must be associated

with the same Windcave Group; for additional information please contact our Support team.

Example Unmatched Refund:

<TxnType>Refund</TxnType>

<VendorId>DPSVendor</VendorId>

<MRef>My Reference</MRef>

</Scr>

Example Matched Refund:

<TxnType>Refund</TxnType>

<VendorId>DPSVendor</VendorId>

<MRef>My Reference</MRef>

</Scr>

Related product manuals