Published 19.06.2015

Problems with 3d-Secure

We are currently experiencing issues with 3d-Secure on both Visa and MasterCard transactions and we are investigating the source of the problems.

Published 12.02.2015

Important information regarding your status webservice with DIBS.

 

DIBS is making some changes to our status webservice feature.

We have identified that your shop is using this feature. If you want to continue to use this service you are required to make some changes.

 

When wil the changes happen

We are planning a release in during mid/end February.

Once we have done the release we advise you to test the integration and make your own release when you are ready.

 

What is new

The main change is of the wsdl-file that will now be using two methods instead of one.

There will be one separate method for getting info by verfyId, and a separate method for getting info by referenceNo.

 

What do I need to do

You will need to generate new web service client using the new wsdl-file and use that client in your code.

The new wsdl-file is attached here

If you have any questions please contact our support: http://www.dibs.se/kundsupport

Published 03.02.2015

Important information regarding DIBS SSL server certificate for payment.architrade.com

 

DIBS will be replacing the SSL server certificate for payment.architrade.com

with a new server certificate. The existing SSL server certificate is issued 

by a Thawte CA and will be expiring on February 25th. 

 

To address this issue, DIBS will replace the Thawte-issued server 

certificate with a new server certificate issued by Thawte.

 

When will the certificate be replaced

The server certificate is scheduled to be replaced between: 

 18/02/2015 08:00 and 18/02/2015 10:00 CET 

 

What are the changes in the new certificate?

DIBS will be moving from SHA-1 Certificates to the SHA-2 Hashing Algorithm. 

You should ensure that your systems support SHA-2. All major browsers support SHA-2, 

and several certificate issuers have made "compatibility lists", eg.

https://www.digicert.com/sha-2-compatibility.htm

 Both the new server certificates and the new intermediate CA certificates can 

be downloaded from our website: 

 

Server certificate: https://cdn.dibspayment.com/ssl/payment_architrade_com.crt

Intermediate certificate: https://cdn.dibspayment.com/ssl/payment_architrade_com_intermediate.crt

 

To ensure that all customers are able to use the system after the switch 

we have set a temporary system up with the new certificate. It will require some 

changes at your end. 

 

How to test

When you have made your tests, then please revert your changes. All new transactions and

modification on existing will happen on productions systems.  

 

On Windows: To use the test setup you will have to manually alter the host file on your 

system to point "payment.architrade.com" to a different IP address.

Point to this IP: 85.236.67.14

On Windows based systems the hosts file is edited as follows:

 * search for notepad.exe

* right click it and select to "run as administrator"

* notepad will now open

* in notepad´s menu select file -> open

* navigate to : c:\windows\system32\drivers\etc\

* in the file name extention dropdown find "Text Documents(*.txt)" and change it to "All Files (*.*)"

* the hosts file should now be visible, double click it to start editing it.

* Add the line to the host file in the same way as on Linux

* Save the file

 

On Linux:  Edit the file “/etc/hosts” as root with an editor of 

own choice, adding the new address to the bottom of the file as follows:

85.236.67.14 payment.architrade.com

Published 19.12.14

Our issue with instability with DIBS Payment Window  is now resolved, and everything is back to normal operation. We are actively investigating the root cause of the issue and will take proper actions.

If you are missing some callbacks related to the issues we had on the 17th and 18th the callbacks will be re-sent during today

Published 18.12.14

On Dec 17th starting around 4:45 PM DIBS experienced issues with the callback mechanism which sends an update to the web shop systems that a payment has been registered.

As a consequence, the customer might not have received an order confirmation from your systems even if the payment was successfully made. The customer might have tried to make a new payment resulting in duplicate authorization or captures.

 

What should I do with duplicate authorizations or captures.

A customer might have made several unique payments for the same order. Any duplicate payments can be cancelled / refunded in the DIBS Administration.

In your DIBS Administration you can find an overview of all accepted payments. We recommend that you manually verify whether the payments in DIBS are linked to a successful order in your systems.

 

If you find a payment in DIBS on an order with incomplete status in the webshop, you can try to manually update the order and capture the transaction in your DIBS Administration.

 

Instability with DIBS Payment window

Starting around 9:25 PM till 11 PM yesterday December 17th and today, December 18th, from 9:30 AM till 9:45AM, an operation disturbance occurred.

Please give us a call at or send an e-mail with any questions or concerns you might have; http://www.dibs.se/kundsupport

Published 11.12.2014

We have identified a problem with the server module some merchants are using towards DIBS. The affected server modules are the COM- and C-versions, which are deprecated and not supported anymore.

How does this affect my shop?

If you are using the affected server module, you might experience problems with API-requests to DIBS. The problem manifests as a SSL Handshake Error.

What is the solution?

We have created a temporary solution that you can use until you are able to implement the permanent solution.

Permanent solution

Migrate from using the server module to using the SOAP Web Service. Documentation is available on our tech-site: http://tech.dibspayment.com/dtapi. The web service has the same functionality as the server module.

Temporary solution

The temporary solution will end 11th of March 2015.

The temporary solution is to point the server module to a new endpoint URL and add new certificates to the trust store used by the server module.

The endpoint URL is passed to the COM-object during initialization by calling the SetURL-method:

void SetURL(BSTR URL)

Example:

Set server = Server.CreateObject("DebiTechServer.DTServer")

call server.SetURL("https://incab.dibspayment.com/verify/server/[ShopName]/")

call server.SetTrusted(“\path\trusted.cer")

call server.SetRandomDeviceFile(“\path-to\random.txt", 500)

The URL should be changed from:

https://secure.incab.se/verify/server/[ShopName]/

to:

https://incab.dibspayment.com/verify/server/[ShopName]/

 

Note that the temporary endpoint URL only supports connections on port 443 and not on port 444 using client certificate. This means that it will not be possible to do refunds.

Besides changing the endpoint URL, you must also edit your trusted.cer file - used when you initiate the COM object. The content of the attached file should be passed into your trusted.cer, which can be edited using Notepad etc.

Afterwards, your web server should be restarted.

To download the certificate right click here

 

Published 11.12.2014

We have identified a problem with the server module some merchants are using towards DIBS. The affected server modules are the COM- and C-versions, which are deprecated and not supported anymore.

How does this affect my shop?

If you are using the affected server module, you might experience problems with API-requests to DIBS. The problem manifests as a SSL Handshake Error.

What is the solution?

We have created a temporary solution that you can use until you are able to implement the permanent solution.

Permanent solution

Migrate from using the server module to using the SOAP Web Service. Documentation is available on our tech-site: http://tech.dibspayment.com/dtapi. The web service has the same functionality as the server module.

Temporary solution

The temporary solution will end 11th of March 2015.

The temporary solution is to point the server module to a new endpoint URL and add new certificates to the trust store used by the server module.

The endpoint URL is passed to the COM-object during initialization by calling the SetURL-method:

void SetURL(BSTR URL)

Example:

Set server = Server.CreateObject("DebiTechServer.DTServer")

call server.SetURL("https://incab.dibspayment.com/verify/server/[ShopName]/")

call server.SetTrusted(“\path\trusted.cer")

call server.SetRandomDeviceFile(“\path-to\random.txt", 500)

The URL should be changed from:

https://secure.incab.se/verify/server/[ShopName]/

to:

https://incab.dibspayment.com/verify/server/[ShopName]/

 

Note that the temporary endpoint URL only supports connections on port 443 and not on port 444 using client certificate. This means that it will not be possible to do refunds.

Besides changing the endpoint URL, you must also edit your trusted.cer file - used when you initiate the COM object. The content of the attached file should be passed into your trusted.cer, which can be edited using Notepad etc.

Afterwards, your web server should be restarted.

To download the certificate right click here

 

Har du frågor eller behöver hjälp?
DIBS Payment Services AB (publ)
Kungsgatan 32
111 35 Stockholm
Telefon: 08-527 525 00
sales@dibs.se


DIBS Payment Services Göteborg
Kyrkogatan 25, vån 3
411 15 Göteborg
Telefon: +46 (0)31-600800
sales@dibs.se