Site integration checklist

Before going live, there are a few things to keep in mind. Various agreements have to be signed, and an amount of information has to be available to the customers in the webshop. In this section you will find a checklist for everything that needs to be done before a webshop can go live. If you guidance in the integration process, please refer to our starter guide

Payment flow

First of all the shop has to be able to open the payment window and handle the response. The integration with the payment solution will need at least the following features:

  1. Be able to post data to FlexWin, opening the window and allowing for card data to be typed.
  2. Handle the response data sent to the return page or callbackurl. Two methods of receiving the response from Nets are possible:
    • Redirect: The outcome of the payment is returned along with the customer
    • Server-to-server: The response is sent directly to the shop system in a "callback", without the need of the customer returning to the accepturl. This has the advantage that the shop gets feedback that a payment has gone through even if the customer closes the browser before reaching the shop.
  3. Show the order receipt both at the page the customer reaches after the purchase and in a mail sent to the customer automatically. This receipt should contain at least the following information:
    • Shop name
    • Contact information
    • Product bought
    • The shop's order ID, which can be used to identify the payment
    • The Nets transaction number
    • Amount drawn
    • Currency
    • Expected delivery date


Acquirer agreement

To be able to carry out live payments, an acquirer agreement must be registered at the Nets account. This may in some cases take several days; for example does 3d-secure enabled acquirer agreements have to be registered externally, adding expedition time.

Website information

Many business partners have demands regarding the processing and handling of online purchases and payments. The legislation on this may vary from country to country, as do the rules and regulations from acquirer to acquirer with respect to the exact details of such demands. We strongly advise you to follow the points given below, since we consider these to be ”best practices”.

Note: It is the responsibility of your business to ensure compliance with local legislation and requirements from acquirers.

Before payment takes place

The following information should be visible to the customer before payment takes place:

  • The shop’s contact info (name, address, e-mail and/or telephone number including the shop’s CVR number).
  • A complete description of the services/products offered. In other words, the customer must never doubt what he/she is paying for.
  • A clear itemization of the total amount charged to the credit card, including freight, value added tax, etc.
  • Specification of the currency used for the transaction (e.g. DKK).
  • Terms of sale and delivery, including the right to terminate the purchase agreement.
  • A clear statement of shipping policies (when will the customer receive the merchandise).
  • All credit card types honoured by the shop must be displayed in graphic form on one of the shop’s pages. Customers use various types of browsers and screen resolutions which should be taken into consideration.
  • 3-D Secure should be displayed wherever this is used.
  • Export restrictions, if applicable.
Confirmation of order/receipt

Once a purchase has taken place, the customer must receive a confirmation of his/her order and a receipt in the form of an on-screen-display and e-mail. As a minimum the confirmation must include:

Immediately following the payment (on the shop’s website):

  • Transaction status (accepted/declined)

AFTER the purchase (on the e-mail order confirmation / e-mail receipt) the customer must be able to find:

  • The name of the shop.
  • The shop’s e-mail address.
  • A complete description of the services/products purchased.
  • An order number (the shop’s internal order reference number).
  • The transaction number (Nets transaction number).
  • The transaction date.
  • The transaction currency (must show the standard international 3-letter code, e.g. DKK).
  • The total amount to be charged to the customer’s credit card (incl. charges, value added tax, freight, etc.).
  • The expected date of delivery.
  • The transaction status (completed/declined).
  • The amount indicated must not exceed the amount quoted in the order form.

Site integration examples

Replace the values surrounded by '*' in the example below with your own values.

    <INPUT TYPE="hidden" NAME="accepturl" VALUE="">
    <INPUT TYPE="hidden" NAME="amount" VALUE="*amount*">
    <INPUT TYPE="hidden" NAME="currency" VALUE="*currency*">
    <INPUT TYPE="hidden" NAME="merchant" VALUE="*yourMerchantID*">
    <INPUT TYPE="hidden" NAME="orderid" VALUE="*yourOrderID*">
    <INPUT TYPE="hidden" NAME="billingAddress" VALUE="*billingAddress*">
    <INPUT TYPE="hidden" NAME="billingAddress2" VALUE="*billingAddress2*">
    <INPUT TYPE="hidden" NAME="billingFirstNAME" VALUE="*billingFirstNAME*">
    <INPUT TYPE="hidden" NAME="billingLastNAME" VALUE="*billingLastNAME*">
    <INPUT TYPE="hidden" NAME="billingPostalCode" VALUE="*billingPostalCode*">
    <INPUT TYPE="hidden" NAME="cardholder_NAME" VALUE="*cardholderNAME*">
    <INPUT TYPE="hidden" NAME="cardholder_address1" VALUE="*cardholderAddress1*">
    <INPUT TYPE="hidden" NAME="cardholder_zipcode" VALUE="*cardholderZipcode*">

In the following replace values surrounded by '*' with your own value.

<FORM NAME="payform" METHOD="post" ACTION="">
  <INPUT TYPE="hidden" NAME="accepturl" VALUE="**" />
  <INPUT TYPE="hidden" NAME="amount" VALUE="*amount*" />
  <INPUT TYPE="hidden" NAME="billingAddress" VALUE="*costumerBillingAdress*" />
  <INPUT TYPE="hidden" NAME="billingAddress2" VALUE="*costumerBillingAdressContinued*" />
  <INPUT TYPE="hidden" NAME="billingFirstName" VALUE="*costumerBillingFirstName*" />
  <INPUT TYPE="hidden" NAME="billingLastName" VALUE="*costumerBillingLastName*" />
  <INPUT TYPE="hidden" NAME="billingPostalCode" VALUE="*costumerBillingPostalCode*" />
  <INPUT TYPE="hidden" NAME="billingPostalPlace" VALUE="*costumerBillingPostalPlace*" />
  <INPUT TYPE="hidden" NAME="cardholder_name" VALUE="*cardholderName*" />
  <INPUT TYPE="hidden" NAME="currency" VALUE="*currency*" />
  <INPUT TYPE="hidden" NAME="distributionType" VALUE="*typeOfBill*" />
  <INPUT TYPE="hidden" NAME="email" VALUE="*costumerEmail*" />
  <INPUT TYPE="hidden" NAME="md5key" VALUE="*calculatedMd5Key*" />
  <INPUT TYPE="hidden" NAME="merchant" VALUE="*yourDibsMerchantId*" />
  <INPUT TYPE="hidden" NAME="orderid" VALUE="*yourOrderId*" />
  <INPUT TYPE="hidden" NAME="structuredOrderInformation" VALUE="*&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;&lt;orderInformation&gt; &lt;orderItem itemDescription=&quot;prod1&quot; itemID=&quot;3363&quot; orderRowNumber=&quot;1&quot; price=&quot;400&quot; quantity=&quot;1&quot; unitCode=&quot;pcs&quot; VATPercent=&quot;0&quot; /&gt;&lt;/orderInformation&gt;*">
  <INPUT TYPE="submit">
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