Knowledge Base

Get help for payment solutions. Search our articles or browse by category below.

5.1.5 Unreferenced Refund

Unreferenced refunds are refunds that do not require a sale transaction to be referenced to. They are only available on certain accounts by request to support@worldnettps.com and must also be approved by your acquiring (merchant) bank. Also they can only be performed on valid Secure Cards.

The following is a simple example of an unreferenced refund via an XML POST:

<?xml version="1.0" encoding="UTF-8"?>
<UNREFERENCEDREFUND>
	<ORDERID>115073134</ORDERID>
	<TERMINALID>6491002</TERMINALID>
	<CARDDETAILS>
		<CARDTYPE>VISA</CARDTYPE>
		<CARDNUMBER>4111111111111111</CARDNUMBER>
		<CARDEXPIRY>0807</CARDEXPIRY>
		<CARDHOLDERNAME>Joe Bloggs</CARDHOLDERNAME>
	</CARDDETAILS>
	<AMOUNT>10.00</AMOUNT>
	<EMAIL>cardholder_email@worldnettps.com</EMAIL>
	<DATETIME>20-06-2006:12:28:02:171</DATETIME>
	<HASH>cfa094f53a508d2031c7895f9f766cbb</HASH>
	<OPERATOR>Test Operator</OPERATOR>
</UNREFERENCEDREFUND>


The following is a simple example of an unreferenced refund on a SecureCard via an XML POST:

<?xml version="1.0" encoding="UTF-8"?>
<UNREFERENCEDREFUND>
	<ORDERID>115073134</ORDERID>
	<TERMINALID>6491002</TERMINALID>
	<CARDREFERENCE>2967534771694736</CARDREFERENCE>
	<AMOUNT>10.00</AMOUNT>
	<EMAIL>cardholder_email@worldnettps.com</EMAIL>
	<DATETIME>20-06-2006:12:28:02:171</DATETIME>
	<HASH>cfa094f53a508d2031c7895f9f766cbb</HASH>
	<OPERATOR>Test Operator</OPERATOR>
</UNREFERENCEDREFUND>


For testing, this XML is posted to:

https://testpayments.worldnettps.com/merchant/xmlpayment



A response for this transaction would be:

<?xml version="1.0" encoding="UTF-8"?>
<UNREFERENCEDREFUNDRESPONSE>
	<RESPONSECODE>A</RESPONSECODE>
	<RESPONSETEXT>SUCCESS</RESPONSETEXT>
	<UNIQUEREF>G53D0M1S4</UNIQUEREF>
	<TERMINALID>6491002</TERMINALID>
	<AMOUNT>10.00</AMOUNT>
	<DATETIME>20-06-2006:12:28:03:875</DATETIME>
	<HASH>6a06aa6f14fe539f4dedd305465811ab</HASH>
</UNREFERENCEDREFUNDRESPONSE>


The Worldnet payment system then handles subsequent transaction settlement and storage.



The following is a description of each field:

Filter:

Field Name Required Description
ORDERID Y A unique identifier for the order created by the merchant. (Max 12 characters).
CURRENCY N A 3 character currency code of the transaction. ISO 4217 Currency Code. Required only for multi-currency Terminal IDs (see section 3.3).
TERMINALID Y A Terminal ID provided by Worldnet. NB - Please contact Worldnet to be issued with a test terminal ID.
CARDREFERENCE N If using a SecureCard then this tag must contain a valid SecureCard Card reference.
CARDDETAILS N If not using a SecureCard then this tag must be populated.
AMOUNT Y The amount of the transaction as a 2 digit decimal or an Integer value for JPY amounts.
AUTOREADY N Y or N. Automatically set the transaction to Ready in the batch. If not present the terminal default will be used.
EMAIL N An email address to send a confirmation email to. Normally this is cardholder email address.
DATETIME Y Format: DD-MM-YYYY:HH:MM:SS:SSS.
HASH Y An MD5 HASH. See note 1 below.
OPERATOR Y An identifier for who executed this transaction.
DESCRIPTION N The description for the refund.


The following fields are returned in the response:

Filter:

Field Name Description
RESPONSECODE A or D (Approved or Declined).
RESPONSETEXT The text of the authorisation.
UNIQUEREF The UNIQUEREF for this refund.
DATETIME Format: DD-MM-YYYY:HH:MM:SS:SSS.
PROCESSINGTERMINAL If the transaction was performed on a “routing terminal” then this is populated with processing terminal ID that the system selected to process the transaction.
HASH An MD5 HASH. See note 2 below.
ADDITIONAL_FIELD This field is used to send back data of interest of the merchant received by the gateway during the transaction. Currently two fields are possible to be returned (see note 3): ACQUIRER_RESPONSE_CODE and ACQUIRER_RESPONSE_TEXT, containing the original code and text from the acquirer's response to the authorization transaction.



Notes:

1. The MD5 HASH is generated using the following as an input string:

TERMINALID+ORDERID+CARDTYPE+CARDNUMBER+CARDEXPIRY+CARDHOLDERNAME+AMOUNT+DATETIME+secret

For multi-currency Terminal IDs (see section 3.3 above) this should be:

TERMINALID+ORDERID+CARDTYPE+CARDNUMBER+CARDEXPIRY+CARDHOLDERNAME+CURRENCY+AMOUNT+DATETIME+secret

If using a SecureCard (CARDREFERNCE tag) then the MD5 HASH is generated using the following as an input string:

TERMINALID+ORDERID+AMOUNT+DATETIME+secret

For multi-currency Terminal IDs (see section 3.3 above) this should be:

TERMINALID+ORDERID+CURRENCY+AMOUNT+DATETIME+secret



2. The MD5 HASH is generated using the following as an input string:

TERMINALID+UNIQUEREF+AMOUNT+DATETIME+RESPONSECODE+RESPONSETEXT+secret

3. This data is going to be retrieved when the Terminal executing the transaction is configured to do so. This configuration can be activated on the Terminal settings, enabling the “Integration” option “Enable original response in XML”.

Copyright © 2018 Worldnet Knowledge Base | Powered by DokuWiki
developer/integrator_guide/5._xml_integration/5.1._request_types/5.1.5._unreferenced_refund.txt · Last modified: 2017/12/08 11:16 by tleite