Return parameters

The input parameters that you provide to DIBS have been described on the Input parameters page. There is also another kind of parameters, system parameters. You don’t provide DIBS with these parameters. DIBS provides them to you. They contain data that DIBS Payment Gateway has created and that can provide some extra information about the purchase to you and your customers

These system parameters can be accessed and used where you can use the input parameters. E.g. in the page sets, in the HTTP reports, in the FTP reports. How you access the system parameters differs slightly from the input parameters. For details see respective chapter.

Tip

The DIBS recommendation is to use the HTTP reports as confirmation that the payment has been accepted (or declined). Please refer to the HTTP_Report chapter to find a detailed description of how to set this up.

HTTP Reports are callback reports which can be sent by the DIBS server when DIBS has decided to set a response on a payment. This can be set up in DIBS Manager.

The HTTP Report is sent from the DIBS server to any server on the Internet. It does not use the consumer browser to send this information. Therefore, this is a safer way to get information about your payments.

Also, DIBS strongly recommends that you use MAC on your HTTP reports as well. This makes it much more difficult to fake these reports. The MAC feature is used as default for HTTP Reports.

Parameters

Parameter Description
authCode

This system parameter contains the authorization code from the acquirer for card purchases. It is a code that the end-user might be interested in getting, especially if there is a problem with the purchase. Example of an authCode: “897128”.

You can only retrieve the authCode for accepted authorizations; simply because it is only those that can have an authorization code.

acquirerResponseCode

This system parameter contains the acquirer's own, unfiltered, response code to a transaction request. These codes are mainly only applicable for credit card authorizations. The code is applicable for some other types of transactions as well. If it is it will be described in that context of the manual. You might be interested in this code as merchant if there was a problem with the transaction and you really want to know the acquirer's reason for declining the transaction.

ccPart

This system parameter enables you to get part of the card number used in the card purchase. The card number is cloaked in order to keep the real card number secret, e.g. “**** **** **** 1234”.

ccPrefix

This system parameter enables you to get the 6 first digits of the card number used in the card purchase. E.g. “491889”.

ccType

This system parameter enables you to get information about what type of card that was used in the card purchase. E.g. “Visa”, “MC”, “AmEx”, “DANCARD”, “MAESTRO”, “Resurs”, “Diners”, “MASTERCARD”, “ELECTRON”, “UNKNOWN”. This parameter is present where applicable.

ccCategory

This system parameter enables you to get information about what category of card that was used in the card purchase. E.g. “Diners”, “Resurs”, “AmEx”, “BANKKORT”, “P”, “MCC”, “J”, “B”, “MSI” and so forth. This parameter is present where applicable.

expM

This system parameter enables you to get information about the card expiry month used in the card purchase E.g. “03”.

expY

This system parameter enables you to get information about the card expiry year used in the card purchase E.g. “12”.

 

Do you have question or need help?
Follow us
DIBS Payment Services
Stockholm +46 (0)8-527 525 00
Göteborg +46 031-600 800
København +45 7020 3077
Oslo +47 21 55 44 00