ticket_auth.cgi

The merchant parameter is the shops DIBS identification number. The merchant number is available in the order confirmation email and is a 7-digit integer.

The value of "transact" returned by auth.cgi or Flexwin.

Amount to be transferred. The amount must be given in smallest possible unit, e.g. cents 100 = USD 1.

Currency code of the transfer in the ISO4217 form, e.g. 208 for DKK (see other ISO4217 currency codes ).

The shops order number, which may contain a maximum of 50 characters.

If this variable is set (e.g. textreply=true) the DIBS server returns its answer in simple text format. If you are not using the standard DIBS payment window, e.g. using server-to-server requests, this significantly simplifies parsing the answer from DIBS.

If several departments within a company use the same acquirer contract, it may be beneficial to keep track of the transactions per department. Setting the "account" parameter enables separation of the transactions by department in the DIBS administration interface.

This variable enables a MD5 key control of the parameters received by DIBS. This control confirms that the parameters sent to DIBS has not been tampered with during the transfer. The MD5-key for auth.cgi is calculated as:

MD5(key2 + MD5(key1 + “merchant=<merchant>&orderid=<orderid>

&ticket=<ticket>&currency=<cur>&amount=<amount>))

Where key1 and key2 are shop specific keys available through the DIBS administration interface, and + is the concatenation operator. NB! MD5-key check must also be enabled through the DIBS administration interface in order to work. Further details on MD5-key control .

This variable indicates to the DIBS server whether the transaction is an actual 'live' transaction or simply a test transaction. If 'test=true' is included in the post to the DIBS server, the transaction is dealt with by a dedicated test-server, and not transferred to the acquirer. See step 5 in the 10 step guide for further explanation. Please note, that during the initial implementation phase all transactions are automatically regarded as test transactions regardless of the test variable parameter. Once DIBS have approved the implementation the test variable must be enabled if testing is performed. Please contact the DIBS support if you require the full test mode to be re-enabled after your payment facility has gone live.

If this parameter is set the DIBS server checks the order number to be unique. That is, if a previous transaction contain the same order number, the authorisation is rejected with reason=7. Unless the shop is unable to create unique order numbers it is strongly recommended to enable uniqueoid. NB! order numbers must be less than 50 characters.

If several departments in a company use the same acquirer contract it may be beneficial to keep track of the transactions by department. Setting the account parameter enables separation of the transaction by department in the DIBS administration interface.

If this parameter is set, the DIBS server tries to capture the transaction immediately following the authorisation (if this was successful). Instant capture is only allowed for shops that sell products that are not physically shipped to the customer, e.g. conferences fees or services on the internet. NB! capturenow requires uniqueoid to be enabled. Please contact DIBS if you intend to use capturenow.

If this parameter is set (e.g. calcfee=foo), the charge due to the transaction will automatically be calculated and affixed, i.e., the charge payable to the acquirer (e.g. PBS)

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

Complex order information. If both simple and complex order information (ordertext) is declared, the simple order information is ignored. This information is stored at DIBS.

Complex order information (please refer to Order information in DIBS). If both complex and simple order information (ordertext) is declared, the simple order information is ignored. This information is stored at DIBS. It is a requirement that the number of fields be identical in all lines of the order. E.g., if there are four fields in the first line, the remaining lines must also contain four fields.

Complex order information. If both complex and simple order information is declared, the simple order information is ignored. This information is stored at DIBS.

string

ACCEPTED

integer

All transactions are given a unique DIBS identification number, it is a as minimum 6-digit integer , e.g. transact=123456.

string

Credit card type used

string

The acquirer authorisation code

integer

The calculated fee only returned if [calcfee] was sent as input

string

calculated as MD5(k2 + MD5(k1 + "transact=<transact>&amount=<amount>&currency=<currency>")) only returned if keys (k1, k2) are activated in the DIBS administration interface
NOTE: 'amount' includes the value of the [fee] parameter if returned

string

DECLINED

integer

Reason for the rejection. Please refer to  error codes for a list of possible values.