Configure

Configuration and testing instructions.

Content

Basic configuration

To configure the add-on, set the attributes in the wwwroot\bin\Litium.Studio.AddOns.Dibs.dll.config file, and change settings in Dibs Manager (Dibs back office).

You need to obtain account details from Dibs before you can configure the add-on.

If wwwroot\bin\Litium.Studio.AddOns.Dibs.dll.config file does not exist, rename the wwwroot\bin\Litium.Studio.AddOns.Dibs.dll.config.tmpl.exclude to wwwroot\bin\Litium.Studio.AddOns.Dibs.dll.config. If the file already exists, merge the change from Litium.Studio.AddOns.Dibs.dll.config.tmpl.exclude into the existing file.
Follow the instructions at the top of the file to set the options.
Log in to Dibs Manager (Dibs back office).
In Hosted Pages > Overview, click Add new page set and select StandardV2 and enter a name without spaces. This name should be entered into the pageSet attribute in Litium.Studio.AddOns.Dibs.dll.config. To manage direct bank payments, you will need a separate pageSet called DirectPaymentV2.
Return Url should be set to https://<your domain name>/PaymentProviderResult.axd/StaticCallback/Dibs (Use Http:// if your checkout page is http).
The check boxes Activate return url and Return all merchant parameters should be checked.
Cancel Url should be set to https://<your domain name>/PaymentProviderResult.axd/StaticCallback/Dibs (Use Http:// if your checkout page is http).
The check boxes Activate cancel url and Return all merchant parameters should be checked.
Save the settings.
In Security > Mac Configuration, create a SHA1 key and set it to active. The value should be entered in the secretWord attribute of the Litium.Studio.AddOns.Dibs.dll.config file. The hash algorithm attribute should be hashAlgorithm="SHA-1".

Back to the top

HTTP reports

HTTP reports in Dibs allow the Dibs server to call back Litium to notify about status changes to payments. This is particularly important if bank payments are made through Dibs. There might be a delay between the initialisation of the transaction and the approval by the bank. In these cases the payment is set to a pending state, and after the bank has approved it (or denied it), Dibs notifies Litium using an HTTP report. If the reports are not configured correctly the payment status in Litium might be incorrect in such cases.

To configure reports, log in to Dibs Manager and go to Reports > HTTP and add a new HTTP(Get) report for all pagesets using the following URL:

http://yourServerDomain/PaymentProviderResult.axd/Report/Dibs?ref=[ver id no]&reply=[ver reply]&replyExt=[ver replyExt]&sum=[ver sum]&referenceData=[ver valueof="referenceNo"]&currency=[ver valueof="currency"]&expY=[ver sysinfo="expY"]&expM=[ver sysinfo="expM"]&authCode=[ver sysinfo="authCode"]&ccPrefix=[ver sysinfo="ccPrefix"]&ccType=[ver sysinfo="ccType"]

Note: You may experience errors in the Dibs report communication if ccCategory=[ver sysinfo="ccCategory"] is included in the query string above, since sometimes the value contain space characters. Please contact Dibs or Litium if you need ccCategory information for integration purposes.

When configured successfully the Dibs payment methods will be displayed in the Litium back office in control panel > Sales > Payment methods.

Back to the top

Multi-market support

The same Litium installation can have multiple Dibs accounts. In Litium.Studio.AddIbs.Dibs.dll.config, add a new paymentAccount section by copying and pasting an existing paymentAccount section.

Each paymentAccount should have a unique paymentAccIdentifier. This identifier should not contain any spaces, and it will be appended to the system name of each payment method. Configure each payment account according to the account information you have received from Dibs, and enable or disable payment methods according to the requirements of your checkout flows.

Back to the top

Masterpass

Masterpass enhances the shopping experience for credit card users by storing the users' delivery and card data at the Masterpass site, so they do have to be entered again. The user logs in to Masterpass with a Masterpass account or with BankID.

Using Masterpass

Due to the difference in UI flow between Masterpass and other payment methods, you need to have Accelerator 4.0 or later for an out-of-the-box Masterpass implementation.

If you do not use the accelerator, you can implement the Masterpass UI flow by implementing Masterpass Quick Checkout Button as done in the accelerator code, and modifying the checkout page to handle the corresponding redirects.

Configuring Masterpass

Provide the following address to Dibs to configure Masterpass:

http://<your domain>/PaymentProviderResult.axd/StaticCallback/Dibs

Then switch on the Masterpass flag in the addon config file and add the Masterpass payment method to your checkout page. If you use the accelerator the Masterpass Quick Checkout Button will automatically appear in the mini-cart.

Back to the top

Testing

Dibs only allows testing using the ccTest method. You will get into the page set you have specified in your config file, so you need to change the config file to get into the desired page set when you test. More information about testing parameters can be found in the Dibs documentation.

Test card details:

Mastercard: 5100100000000000
Visa: 4711100000000000
- Prefix: 4711
- Code for approval: 100000000000

Testing Dibs direct bank payments

The Dibs plugin supports direct bank payments. However, due to the technical nature of the integration Dibs has with the banks, it is not possible to create test orders. The orders have to be created with the live account.

Therefore the implementation project should test each direct bank payment method used in production with the merchant's live account. Before making any test transactions, notify both Dibs and the bank so that the test transactions are not considered as real.

Back to the top