FlexWin (Method 1)

- Return pages

As mentioned previously, the user can exit FlexWin one of two ways:

1. The customer returns to "accepturl" once the payment is approved.
2. The customer cancels the payment, and is returned to "cancelurl".

Note: The security updates of recent browsers has necessitated, that the shop's accept/cancel page is shown in the popup window. From there you may have an optional link (or autoloader) to the originating window. This is done by naming the calling window and using this name as a link target on the accept/cancel page.

Payment approved (accepturl)

Upon returning to accepturl, the customer will normally expect a receipt to be displayed. We therefore recommend you use the accepturl option for generating a customer receipt. Aside from the standard port 80, accepturl may also use port 20080. The following parameters are returned to the accepturl:

Payment cancelled (cancelurl)

As is the case with the accepturl, a post is made to the ”cancelurl” page with all previous parameters sent to the DIBS FlexWin. CGI-parameters sent to the cancelurl are also returned (?x=1&y=4). Again, aside from the standard port 80, cancelurl may also use port 20080. Note: Reserved words cannot be used as declared cgi-parameters (see list of reserved words).

Automatic call-back (callbackurl)

There is a potential risk of the customer not following the link to the receipt and subsequently never seeing one. If the shop system is set up so that orders are stored in the database simultaneously with the receipt being displayed to the customer, the order may in fact escape registration within the shop’s own system. This would be rather unfortunate, since a payment is authorized with DIBS, the customer believes DIBS has authorized the payment, and the customer believes that the order has been carried out, yet the shop’s system has no knowledge of any such order. 

To avoid such an occurrence, DIBS automatically enables the approved page to call a script in the shop’s system without involving the customer in the procedure. As is the case with the receipt page, this script must inform the shop’s order system, that the order has been carried out, and send an order confirmation to the customer, if required. It can also serve as an MD5 key control to ensure that the customer himself does not call the script, resulting in the shop interpreting the order status as “carried out”.

In order to activate the automatic call-back, a call-back URL must be passed to FlexWin. This is done through the callbackurl parameter. The URL is then automatically called when the approval page is displayed. The call is created as a post, and all parameters are sent to start.pml. CGI parameters sent along to callbackurl (?x=1&y=4), transact, and the MD5-encryption key can be sent along (the same parameters that are returned via accepturl are always sent along). As with accepturl and cancelurl, callbackurl may also use port 20080.

Note: Reserved words cannot be used as declared cgi-parameters (see list of reserved words). If the callback script depends on cookies or a session ID, these must also be sent along to FlexWin in the http_cookie parameter. The value of this variable must be of the form: name1=value1; name2=value2...

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.

ASP:

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

PHP4:

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

or

printf('<input type="hidden" name="HTTP_COOKIE" value="%s">',
  getenv("HTTP_COOKIE"));

JavaScript:

<script type="text/javascript">
<!--
  document.writeln('<input type="hidden" name="HTTP_COOKIE"
  value="' + document.cookie + '">');
//-->
</script> 

Voucher return parameters

When using vouchers, some of the regular return parameters are changed, and new ones are introduced. For example, using a voucher will change the "amount" parameter from what was sent to FlexWin — "amount" now holds the reduced amount.

Please note, that in order to receive the voucher specific return parameters, you must enable the return of additional parameters in DIBS Admin.

The following additional parameters are returned to the accepturl: