Return parameters

Here you can find the standard return parameters for the "accepturl", "callbackurl" and "cancelurl"

Please note that more return parameters can be returned in excess of the below mentioned parameters. Most of these parameters are used internally by FlexWin and have no specific use, but some can be acquirer specific.

Parameters

Standard

Parameter Type Desciption
acquirer String. Max 10 characters Returns the acquirer used for the specific transaction.
agreement  

Returns the acquirer agreement ID.

Optional, please refer to return parameter configuration.

amount long - Minimum value of 1- maximum value 1715000000

Returns the amount without the fee.

Optional, please refer to return parameter configuration.

approvalcode String. Max 6 characters

Returnes the approvalcode from the acquire if available.

authkey  

The MD5 check sum for verification of the authenticity of the transaction. This is only returned if an MD5-key is created within the administration (under installation + MD5 keys). You may read more about MD5 key control.

Note: When using a payment window and the calcfee function, amount+fee is used as a basis for calculations rather the amount only.

cardcountry  

Returns the nationality of the card in "ISO 3166-1 alpha-2" standard.

Example:

cardcountry=DK

Optional, please refer to return parameter configuration.

cardexpdate String. Max 4 characters

Returns the expiry date of the card in the fomat "yymm".

Optional, please refer to return parameter configuration.

cardId String

Returns a unique hash value for the card used for payment. This hash will be unique for all cards on the same merchant and different for two merchants even though the same card is used. The cardId can be used to check if a card has been used for a previous purchase in the shop.

Note: This feature requires activation by DIBS. Please contact our support if you would like this feature.

cardnomask string. Max 50 characters

Card number with no spacing.

Example:

cardnomask=XXXXXXXXXXXX1234

Optional, please refer to return parameter configuration.

cardprefix string. Max 6 characters

Returns the 6-digit prefix of the card used in the transaction.

Example:

cardprefix=123456

Optional, please refer to return parameter configuration.

checksum string. Max 32 characters

Checksum returns a unique value for the card used for the payment.

The checksum will be the same for the card regardless of which DIBS Merchant ID the transaction is made towards.

 
currency String - 3 characters.

Returns the currency used in the transaction.

Example:

currency=208
currency=DKK

Optional, please refer to return parameter configuration.

fee integer

When calcfee is used, the calculated fee is returned so it can be shown on the receipt.

Optional, please refer to return parameter configuration.

orderid String. Max 50 characters.

The shop’s order number for this particular purchase. It can be seen later when a payment is captured, and will in some instances appear on the customer’s bank statement (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.

Optional, please refer to return parameter configuration.

paytype string. No max length

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

Example:
If the payment is made with a VISA card, this parameter will return value="VISA"

See possible paytypes here

Optional, please refer to return parameter configuration.

severity integer

Is returned if fraud control has noted the transaction as a potential fraud, if there is a subscription to fraud control and if this is activated in the DIBS Administration interface.  The higher the number, the more questionable the transaction.  We generally recommend closer checks of transactions with severity > 5.
Activated in DIBS admin in:
Integration / Fraud Protection

Note: DIBS is not responsible for the use of this service and can not guarantee that all attempts of fraud are caught.

Activated in DIBS Admin in "Integration" / "Fraud Protection"

statuscode string

A value describing the result.

A complete list of possible statuscodes are listed here.

Optional, please refer to return parameter configuration.

suspect boolean Is returned if there is a subscription to fraud control and this is activated in the administration interface (in such a case, this may have the value ”true”).
Activated in the DIBS Administration in:
Integration / Fraud Protection
threeDstatus integer

If the card used to pay is enrolled in 3D secure, this parameter will contain a value corresponding to the following:

Value Description
0 Success: The cardholder completed authentication correctly. Card should be accepted for payment and authentication information passed to authorization processing.
1 Attempt: The cardholder is not participating, but the attempt to authenticate was recorded. Card should be accepted for payment and authentication information passed to authorization processing.
2 Failure: The cardholder did not complete authentication and the card should not be accepted for payment.
3 Error: A system error prevented authentication from completing.
4 Not enrolled: The card was not enrolled.

Note: This only works if you are using a 3D secure agreement with the acquire.

Optional, please refer to return parameter configuration.

transact integer, minimum 6 ciffor.

The unique DIBS identification number for the transaction. The transact is a as minimum 6-digit integer, e.g. transact=123456.

 

Voucher

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 to hold the reduced amount after the voucher calculation.

Please note:
In order to receive the voucher specific return parameters, you must configure the "All fields exclusive of card information..." in the DIBS Administration interface.

The following parameters are returned to the accepturl with the following values:

ParameterDescription
amount

This is the amount with the customer have paid with the voucher, which is the original amount sent to FlexWin minus the discount obtained through the voucher.

Example:
FlexWin was called with an amount of 5000 (50DKK) and a voucher gave a 15% rebate. Then "amount" will be 4250.

amount_originalThis is the amount originally sent to FlexWin. If the example above is taken into consideration, this parameter will contain the value="5000".
voucherIdentical to the parameter sent in the call to FlexWin to enable vouchers.
voucher_amountThis is the part of the original amount that is covered by the voucher. If the above example is taken into consideration the value would be "750".
voucher_entryThis is the voucher code that has been entered by the customer.
voucher_rest
The "voucher_rest" parameter only applies to vouchers that hold a fixed monetary amount. If the voucher is reusable and not all of its monetary value is spent, then "voucher_rest" holds the amount that is left on the voucher.
Example:
The voucher used is of type "fixed"; it's maximum number of uses has not yet been reached; before the purchase it held 100DKK (in minor unit "10000"); the purchase used 25DKK (2500) from the voucher. In this case "voucher_rest" will contain 7500.
Furthermore, this parameter is only returned if the voucher can be reused. If the voucher cannot be reused the amount_rest will be unavailable.

 

makeTicket

Make ticket is a function that allows you to do a regular transaction followed by a ticket registration.

When using the input parameter "makeTicket" in combination with 3D-Secure activated at the acquirer, the return values will differ as follows:

The returned values to the accepturl will contain both the transaction ID and the ticket ID e.g. "transact=123456789&ticket=123456789".

The returned values to the callbackurl (if specified) will also contain both the transaction ID and ticket ID e.g. "transact=123456789&ticket=123456789

makeTicket

Make ticket is a function that allows you to do a regular transaction followed by a ticket registration.

When using the input parameter "makeTicket" without 3D-Secure activated at the acquirer, the return values will differ as follows:

If the "callbackurl" is defined in the call to FlexWin:

Two callbacks are made, one with information about the regular transaction and one with information about the ticket transaction.

The regular callback contains a "transact" parameter, which is the transaction ID for the regular transaction.

The ticket callback also contains a "transact" parameter, but contains an additional "preauth" parameter. The "transact" parameter here contains the ticket ID instead of the transaction ID. This callback also returns the "statuscode" parameter with the value "13" (see how to activate the statuscode here).

When the customer is redirected to the "accepturl" both the ticket number and the transaction number is given in the response.

If the "callbackurl" is not defined in the call to FlexWin:

All information is sent to the "accepturl", both the ticket and transaction number. The parameters "ticket" and "transact" sent to the "accepturl" represent the ticket and transaction number.

preauth

When using the parameter "preauth" the transaction will become a ticket transaction, where the payment information is saved for later use.

When the customer is redirected to the "accepturl" the parameters parsed along will contain "transact", that in this case will be the ticket number and the "statuscode" parameter will return the value "13" (see how to activate the statuscode here).
This change applies to the "callbackurl" the same way as the "accepturl".

Please read about preauth here

Barclays

Barclays supports AVS, but an automatic decline is not possible through DIBS.

To use AVS through Barclays, the response is returned to the shop, through both "accepturl" and "callbackurl" has an additional parameter called "avsstatus" that has 6 digit value. This value contains the result of the AVS check, so the shop can choose to decline a payment.

To read this value, use the following table:

PostionFeature
First position - CVC (This is checked and used by DIBS to decline payments as standard)ValueStatus
1Not checked
2Matched
4Not matched
8Reserved for the UK Cards Association
Second position - PostcodeValueStatus
1Not checked
2Matched
4Not matched
8Reserved for the UK Cards Association
Third position - Address numericValueStatus
1Not checked
2Matched
4Not matched
8Reserved for the UK Cards Association
Fourth position - Authorising entityValueStatus
1Not checked
2Matched
4Not matched
8Reserved for the UK Cards Association
Fifth position - Reserved for the UK Cards AssociationValueStatus
1Reserved for the UK Cards Association
2Reserved for the UK Cards Association
4Reserved for the UK Cards Association
8Reserved for the UK Cards Association
Sixth position - Reserved for the UK Cards AssociationValueStatus
1Reserved for the UK Cards Association
2Reserved for the UK Cards Association
4Reserved for the UK Cards Association
8Reserved for the UK Cards Association

If the parameter returned is as the following example:

avsstatus=211800

This means:

avsstatusresult
2Matched (CVC is correct)
1Not checked (not possible to check)
1Not checked (not possible to check)
8Reserved for the UK Cards Association (Not supported by the card)
0Not supported
0Not supported

Se how to setup AVS here

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