Standard parameters

The URL of the page to be displayed if the purchase is approved.

You cannot use parameters in the URL. Example. ”?X=4&Y=2” The URLs have to be ”clean".

Example:

If the payment is accepted, then the customer will be redirected to

It is recommended (but not required) to use HTTPS. 

The smallest unit of an amount in the selected currency, following the ISO4217 standard (see the minor unit list here).

Example:

An optional (but recommended) ”server-to-server” call. Can be used for many purposes. The most important being that you will be able to register the order in your own system without depending on the customers browser hitting a specific page of the shop. Please refer to the return page documentation for further information.

Note: If the shop uses cookies to keep track of the user, see the HTTP_COOKIE parameter.

Currency is defined using the ISO4217 standard (see the currency list here). 

Example:

The shops order number for a particular purchase. This is the cross reference between the shop and Nets (both numerals and letters may be used). The actual length of the orderid shown on the bank settlement report may differ from acquirer to acquirer.

The customers billing street address. If the acquirer requires the address to be entered, then billingAddress is used to prepopulate the address field. If the acquirer returns a different address, billingAddress will be overwritten.

Customers billing street address (continued).

Customers billing first name.

Customers billing last name.

Customers billing postal code

Customers billing postal place (city, town, etc).

Name of the cardholder 

Note: This is required by Wirecard Acquirer service

Customers E-mail address 

Note: This is required by Invoice payment and P24 Acquirer service

This variable enables an MD5 key control of the values received by Nets. This control confirms that the values sent to Nets has not been tampered with during the transfer. See how MD5 is calculated here

Note: When using MD5, the order id must be unique.

acquirerinfo

String. Max 15 characters

If multiple departments utilize the same Nets account, it may be practical to keep the transactions separate at Nets. An account name may be inserted in this field, to separate transactions at Nets.

To get an account, please contact the Nets sales department.

Can be used to specify the language in the acquirers site, e.g. an invoice or netbank window. 

Both lower and upper case short and long language codes are accepted, i.e. "en", "EN" and "en_GB" all result in English.

Note: this parameter is only relevant if your acquirer supports the language localization feature.

If this parameter is sent with the value "yes", the charge from the acquirer due to the transaction will automatically be calculated and affixed.

Fee calculation method: Fee = Amount * Percent / (100-Percent)

NOTE: To use this parameter you need to contact Nets Support with the fees you have at your acquirer, as they need to be entered into our system.

More information about using calcfee with surcharge here

If this field exists, a capture request is automatically carried out after the authorization, following the normal capture process of the specific acquirer.

If a transaction is marked as suspect, the automatic capture request is cancelled and you need to handle the capture.

If used, the order id has to be unique at all times.

Specifies which of the pre-built decorators to use. Possible values are "default", "basal", "rich" and "responsive" ("Responsive" results in a new design created by Nets, which makes the payment window scale automatically to various devices and screen sizes. You must set icons to Large in your Nets Admin).

Example:

Cookies/sessions which are to be sent to the callbackurl and accepturl must be sent along if you are depending on cookies/sessions for keeping track of the user.

If you wish to transfer all declared cookies, the content of the HTTP_COOKIE variable can be used, containing all the cookies in the correct format. Below are a few examples of how to do this in ASP, PHP4 and JavaScript.

<input type="hidden" name="HTTP_COOKIE" value="<%=Request.ServerVariables("HTTP_COOKIE") %>" />

<input type="hidden" name="HTTP_COOKIE" value="<?= getenv("HTTP_COOKIE");?>" />

<form onsubmit="(
function(form){
  el = form.elements['HTTP_COOKIE'];
  document.cookie ? el.value = document.cookie : el.value = '';
})(this)">

  <input type="hidden" name="HTTP_COOKIE" value=""  />
  <!-- insert the rest of the inputs here -->
</form>

Nets retains the IP-address from which a card transaction is carried out. The IP-address is used for ’fraud control’, etc. Some implementations may send the IP-address of the shop to Nets rather than that of the customer's machine. In order to provide the same services to shops which utilize such a program for their Nets hookup, we offer the option of sending the “ip” parameter.

This parameter determines the language in which the page will be displayed. The following values are accepted:

da=Danish

en=English

de=German

es=Spanish

fi=Finnish

fo=Faroese

fr=French

it=Italian

nl=Dutch

no=Norwegian

pl=Polish (simplified)

sv=Swedish

kl=Greenlandic

Default language is Danish.

notifyurl

String

Some acquirers might take a period of time before the payment is accepted. This parameter can be used to specify a callback URL to get a response at a later time when the transaction is either accepted or declined. 

Simple order information sent to Nets in one text string. This information is displayed in the Nets administration interface.

Can be used to limit the accepted paytypes. If set, only the specified paytypes will be accepted, all other will be rejected with reason=10.

Example:

See our list of possible paytypes

Used to register the transaction origin. Default value is "ssl" (internet). The following values are possible:

ssl = internet transactions,

magnetic = magnetic stripe read, and signature is available,

magnosig = magnetic stripe read, and no signature is available,

mail = mail order,

manual = manually entered,

phone = phone order,

signature = card and signature available, manually entered.

String​

The "mitType" parameter is used to store the creditcard info for future payments. A future payment can only be initiated by the merchant (MIT - Merchant Initiated Transaction).​.​

Possible values

• mitType=RECURRING
• mitType=UCOF

(Note: the "preAuth" parameter will default to mitType=RECURRING).​

A transaction initiated with the mitType parameter, can be used for future transactions via ticket_auth.cgi or the NETS BULK solution.​

number​

This parameter can used for processing future payments via the Flexwin Payment Window.​ The ticket ID refers to a previous stored card based on a initial payment procesed with the COF parameter.​

The Flexwin Payment window then display a masked creditcard and expiry date.​ The cardholder is required to enter CVC​.

This refers to scenario 3 (https://www.dibspayment.com/sca)​

String. Only "true" is allowed

When preauth=true is sent as part of the request to auth.cgi the Nets server identifies the authorisation as a ticket authorisation rather than a normal transaction. Please note that the pre-authorised transaction is NOT available among the transactions in the Nets Administration interface.

For preauth to work, Nets has to be contacted for activation.

When using MD5 the Authkey must be calculated from the string transact=12345678&preauth=true&currency=123

NOTE: You cannot use "capturenow" along with "preauth".
Previous "COF" was an alias for preauth.

String. Only "true" or "yes" is allowed

zero_auth is used together with the preauth parameter. zero-preauth ensures that card registration is done via account verification instead of a 1-unit-currency request.

Usage of preauth alone uses 1-unit-currency to register the card. This is not compliant. In order to be compliant towards card schemes merchant must add the zero_preauth parameter.

This parameter is part of complex order information. If both complex and simple order information [ordertext] is declared, the complex order information will be ignored.

This information is displayed in the Nets Administration interface.

When this field is declared, the transaction is not dispatched to the card issuer, but is instead handled by the Nets test environment. When the shop goes live, the test system is normally disabled, and should the shop want to use the test mode at a later date the Nets support can be contacted for reactivation.

String. Max 20 characters

When doing ticket registration, and you have predefined ticket rules (see configuration in Nets Admin / "Subscription" / "Rules") you can set the value of this parameter to be one of the defined rules.

If this parameter is present, the parameter orderid has to be unique compared to all other orderid's used by the merchant.

If the orderid isn't unique, the call will be declined by a reason=7.

If set to "yes", it will be possible to chose "Voucher" as a payment type in FlexWin. Vouchers are created through the Nets Admin, and allows for vouchers of static amounts or percentages. Note that voucher are available only for DKK, SEK, NOK, EUR, GBP & USD.