Knowledge Base

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

5.1.3 Pre-Auth Completion Request

Example of a Pre-Auth completion request:

<?xml version="1.0" encoding="UTF-8"?>

For testing, this XML isn posted to:

A response for this transaction would be:

<?xml version="1.0" encoding="UTF-8"?>

Pre-Auth Completion request fields description:


Field Name Required Description
UNIQUEREF Y A unique identifier for the order created by the merchant. (Max 12 characters). The UNIQUEREF for the original authorisation.
TERMINALID Y A Terminal ID provided by Worldnet.
AMOUNT Y The amount of the transaction as a 2 digit decimal or an integer value for JPY amounts.
FOREIGNCURRENCY INFORMATION N Tag contains Dynamic Currency Conversion information. It is required when completing out of the 15% margin eDCC transaction. See XML Payments with eDCC.
DESCRIPTION N An optional description, overrides original pre-auth description if available.
CVV N The security code entered by the card holder. It should be available when CVV is enabvled for the terminal and completing out of the 15% margin transaction.
HASH Y An MD5 HASH (See note 1 below).

The following fields are returned in the response:

Field Name Description
RESPONSECODE “A” (APPROVED/ AUTHORIZED/ ACCEPTED, respectively), “D” (DECLINED), “R” (REFERRED, also considered as PICKUP), “C” (PICKUP, also known as Referral A or Referral B), and for more details, look at Transaction Responses.
RESPONSETEXT The text of the authorization
APPROVALCODE Six digit AuthCode.
DATETIME The time of the transaction created by the bank. Format: YYYY-MM-DDTHH:MM:SS. Note that this is intentionally in a different format to the request timestamp to highlight the fact that it is a different time.
AVSRESPONSE The result of the AVS check. See Appendix A for more information.
CVVRESPONSE The result of the CVV check. See Appendix A for more information.
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.


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


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


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


Errors handling

If there is an error processing the transaction, the error string is returned in an XML message with the simple:

Copyright © 2018 Worldnet Knowledge Base | Powered by DokuWiki
developer/integrator_guide/5._xml_integration/5.1._request_types/5.1.3._preauth_completion.txt · Last modified: 2018/02/22 17:48 by tleite