Knowledge Base

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

6.2 Secure Card Registration and Updating From the Hosted Page

Secure Card details can be registered or updated using the Worldnet hosted page by the cardholder, card details will be stored using Worldnet Secure Card Storage.

To initiate a Secure Card registration or update a POST must be made to the following URL:

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

The following table describes the form fields to be posted:

Filter:

Field Name Required Description
ACTION Y - register
- update
TERMINALID Y A Terminal ID provided by Worldnet. NB - Please contact Worldnet to be issued with a test terminal ID.
MERCHANTREF Y Unique reference assigned by the merchants site/software to identify the stored card details. Length is limited to 48 chars.
PERMITTEDTERMINALS N List of permitted terminals. Comma separated list without spaces. (See section 6.1 above)
DATETIME Y Format: DD-MM-YYYY:HH:MM:SS:SSS.
HASH Y An MD5 HASH. See note 1 below.


Notes:

1. If permitted terminals are not used, the Md5 HASH is generated using the following as an input string:

TERMINALID+MERCHANTREF+DATETIME+ACTION+secret


2. If permitted terminals are used, the MD5 HASH of the request is generated using the following as an input string:

TERMINALID+MERCHANTREF+PERMITTEDTERMINALS+DATETIME+ACTION+secret



Below is an example HTML form to open card details registration page:

<html>
	<body>
		<form action="https://testpayments.worldnettps.com/merchant/securecardpage" method="post">
			<input type="hidden" name="ACTION" value="register" />
			<input type="hidden" name="TERMINALID" value="6491002" />
			<input type="hidden" name="MERCHANTREF" value="1234321" />
			<input type="hidden" name="DATETIME" value="15-03-2006:10:43:01:673" />
			<input type="hidden" name="HASH" value="d5d3441fb0e8318ce6d03976c2e93749" />
			<input type="submit" value="Register" />
		</form>
	</body>
<html>



To initiate card details updating, the value of the ACTION parameter should be changed to “update”. A Secure Card of MERCHANTREF 1234321 must be already existing under your account. Please note that the TERMINALID here is not valid and must be changed.

Assuming valid details were sent, the Hosted Registration or Update page will be displayed, clicking on “Register” or “Update” will save the card details, result GET parameters will be forwarded to the Secure Card URL that is configured on the Terminal Setup page.

Following parameters will be sent to the Secure Card Receipt URL:

Filter:

Field Name Description
RESPONSECODE Response Code “A” - Approval, check the Response Codes table below for a full list of all supported codes.
RESPONSETEXT Response Text.
MERCHANTREF Original Merchant Reference.
CARDREFERENCE Generated Card Reference.
MASKEDCARDNUMBER The card number (obfuscated) that registered/updated.
CARDTYPE See section 3.2 above.
CARDEXPIRY Expiry date of the card.
DATETIME Format: DD-MM-YYYY:HH:MM:SS:SSS.
HASH An MD5 HASH. See note 1 below.



Notes:

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

TERMINALID+RESPONSECODE+RESPONSETEXT+MERCHANTREF+CARDREFERENCE+DATETIME+secret



Response Codes:

Filter:

Error Code Description
E01 SYSTEM ERROR - TRY AGAIN
E03 OPERATION NOT ALLOWED
E04 INVALID REFERENCE DETAILS
E05 INVALID CARD TYPE
E06 INVALID TERMINAL ID
E07 METHOD NOT SUPPORTED
E08 INVALID MERCHANTREF
E09 INVALID DATETIME
E10 INVALID CARDNUMBER
E11 INVALID CARDEXPIRY
E12 INVALID CARDHOLDERNAME
E13 INVALID HASH



If invalid parameter values are sent, an Error Page will appear and the web browser will not be redirected to the Secure Card Receipt Page. This should not happen in a production environment after integration is completed.

Copyright © 2017 Worldnet Knowledge Base | Powered by DokuWiki
developer/integrator_guide/6._secure_card_storage/6.2._hpp_secure_card_integration.txt · Last modified: 2016/07/27 10:11 (external edit)