HTTP reports

For the shop, http reports are the most secure way of obtaining reports about payments. Using http reports, the shop can automate the entire payment process. The shop has a program (Servlet, JSP, ASP, or equivalent) on its web server, which receives and handles calls from Nets after each order. 


To create an HTTP report, go to Nets Manager and click on Reports > HTTP. Then, choose Add new HTTP report and HTTP (Get) or HTTP (Post) as the report type, depending on how you want Nets to call your server (GET sends data in the URL and POST sends data separately). An empty form is created for the http report. Enter the page set to which the report should be applied (if you’ve got more than one page set) and after which type of verification the report is to be sent: OK, declined or in both cases.
If you have chosen HTTP (Get), the URL field should contain the entire URL including the parameters with URL coding:

http://YourURL/ReceivingPage?DTrefNo=[ver id no]&reply=[ver reply]&sum=[ver sum]&firstname=[ver valueof url=”billingFirstName”]&lastname=[ver valueof url=”billingLastName”]

To URL-encode parameters use the tag [ver urlencode text="[ver parameter name]"]. If you have chosen HTTP (Post), then enter the URL in a separate field. In the parameters field, enter one parameter per line on the form of “parameter name=parameter value”, with URL-coded values. URL:


Parameters: (one parameter per line)

DTrefNo=[ver id no]
reply=[ver reply]
sum=[ver sum]
firstname=[ver valueof url=”billingFirstName”]
lastname=[ver valueof url=”billingLastName”]

Parameters that should be entered in the return report are

“response” ([ver reply]), “total” ([ver sum]), “reference” ([ver id no]

and possibly a specific order number. In addition, name details should be included

([ver valueof url=”billingFirstName”] and [ver valueof url=”billingLastName”]).

When sending your parameter values, don’t forget to URL encode them (by using [ver table description url] for example). Refer to Appendix C: for more details about URL encoding.
To confirm that the report has been received, the reply page must somewhere contain the string “VerifyEasy_response:_OK”, e.g. as an html comment. <!-- VerifyEasy_response:_OK -->
If this string is not included in the reply, e.g. due to temporary server overload, the system will retry sending the report (up to 25 times). If it has still not been received properly, we will send the report to the e-mail address you have entered in the e-mail field under the tab Reports > Http. If there is no value in this field the report will be e-mailed to the Administrator instead. The same applies if the call does not get through, perhaps due to network problems.

Some reasons for not receiving the http report:

  • Your firewall is not set to receive reports, from IP-address
  • Your firewall is password protected
  • You’re trying to get the http report sent to an https-URL which does not support the same ciphers that we use. You can find the list of supported ciphers here

Transactions made using the cc.test acquirer will create a HTTP report just like regular production purchases.

Do you have a question or need help?
Follow us
Nets Online Payments

Oslo: +47 21 55 44 00
Stockholm: +46 (0)8-527 525 00
København: +45 7020 3077
Jyväskylä: + 358 010 80 40 40
Close menu