Operating status

Current operating status of the Bank Connect solution:

Current Operation

Bank Connect is in normal operation in production

We are currently testing a new operational status site. Check it out here: Bank Connect Status *****************************************************************************

Current information on operations and service windows:

22.10.2026 08:00: Some users are experiencing a "500 Internal Server Error" when retrieving extracts via NBS. We are currently working on a solution.

Historic information on operations and service windows:

SOLVED 18.09.2026 11:50-00:00: Bankdata is down in production. All calls are failling with 500 errors.

Bankdata: Due to production issues yesterday, Thursday, September 17, some customers may have missed account statements/extracts. Therefore, Bankdata has marked all statements that were attempted to be collected between 12:00 and 00:00 as available for collection again.

If you have missed any statements, you can now retrieve them again. However, please be aware that this may also result in receiving duplicate statements.

SOLVED 17.09.2026 12:00 - 00:00: Bankdata is down in production. Most calls are failling with 500 errors.

NBS will be merging Nordfyns Bank with Middelfart Sparekasse during the coming weekend. All Nordfyns Bank customers have been asked to retrieve a new Function ID and passcode from the morning of Monday, September 14. During the merger window, Nordfyns Bank users will see the following error message:  

701 – Identification failed.

SOLVED 11.08.2026 22:45 - 12.08.2026 10:40: The Bank Connect test system is down. We are working on a solution.

SOLVED 18.06.2026 12:00 - 13:20: The Bank Connect test environment is down. We are working on a solution.

SOLVED 16.06.2026 09:35 - 12:00: The Bank Connect test environment is down. We are working on a solution.

SOLVED 09.06.2026 01:00 - 10.06.2026 15:45: The Bank Connect test environment is down. All calls are failing with 504/500. We are working on a solution.

BEC will be merging SparNord this following week. All SparNord customer will be temporarily blocked starting Wednesday 1st of April at 18:00 CET and continuing through Tuesday the 7th of April. During the merger window SparNord users will see the following error message:
500#The user is under migration, and is unavailable for use. Please try again later.

SOLVED 16.04.2026 00:01 - 06:10: About half the calls to NBS/SDC is failing.

SOLVED 2002.2026 19:30 – 21:00: All calls to the HUB returned errors/timed out.

SOLVED 21.01.2026 10:40 - 12:02: You may experience that calls to BEC returns 500 errors or timeouts

SDC / Netcompany Banking Services has extended the service window on the night of Sunday, January 18, 2026, from 2:00 AM to 6:00 AM.

SOLVED 16.12.2025 08:00 - 11:30: Bankdata is working on clean up after down time

SOLVED 15.12.2025 18:00 - 23:30: Calls are getting a 500#Internal server error or 504 timeout response. We are working on a fix.

SOLVED 04.12.2025 12:00 - 14:00: You may experience that calls to BEC returns 500 errors or timeouts

SOLVED 03.12.2025 11:10 - 12:00: You may experience that calls to BEC returns 500 errors or timeouts

SOLVED 02.12.2025 09:10 - 13:45: You may experience that calls to BEC returns 500 errors or timeouts

SOLVED 25.11.2025 07:40 - 15:00: Some calls to BEC are returning 500 errors or timeouts

Tests will be carried out from November 8, 2025 at 00:00 until Saturday, November 9 at 08:00, which may affect operations.

SOLVED: In the test environment, not all pain.002 files are currently being generated. We are working on a solution.

SOLVED 08.11.2025 02:09 - 02:49: BEC and Bankdata is returning timeouts and errors.

All three centrals have a service window on Sunday, 26th of October 2025 to adjust from Daylight Saving Time (CEST) to Standard Time (CET).
All systems will be unavailable, and transactions will not be processed between 02:00 CEST and 03:30 Standard Time (CET).

SOLVED 17.10.2025 13:00: The test environment is currently down. We are working on a fix.

SOLVED 15.10.2025 19:15: Approximately 10% of the CAMT extracts from Bankdata banks encountered errors on October 15th. Bankdata has since generated new deliveries to replace the erroneous ones.

SOLVED 09.10.2025 13:40 - 14:20: All calls are getting a 500#Internal server error response. We are working on a fix.

SOLVED 07.10.2025 12:45 - 07.10.2025 13:10: Some calls are failing in production with 500 Internal Server error.

SOLVED 01.10.2025 14:30 - 02.10.2025 16:20: All calls are failing with 503 Service Unavailable in our test environment.

SOLVED 14.09.2025 02:25 - 15.09.2025 08:30: Approximately half of all calls to Bankdata are currently returning error code 633 Unexpected error.

SOLVED 02.09.2025 22:15 - 03.09.2025 8:33 All calls to Bankdata return an error 633: Unexpected error.

SOLVED af 13:40 PM 08.08.2025 TransferPayment Requests towards SDC are currently returning a 500 Internal error - contact Bank Connect support

SOLVED July 10, 2025: Extracts (CAMT52, CAMT53, and CAMT54) from Bankdata’s banks, generated between 1:40 PM yesterday and 10:30 AM today, have been affected by an error. The error causes the extracts to contain one or more "2" characters, rendering them invalid. Additionally, some extracts end with invalid characters (Hex: 0x00).

Update – July 11, 2025: The affected extracts were regenerated and made available from Thursday evening. However, there may still be individual customers who are missing data. These customers are advised to contact their own bank for clarification.

SOLVED: 05.07.2025 6:21 - 7:40: All calls are currently getting a 500 error back. We are working a sollution.

25.06-2025 Payments to SDC accounts are now processing as expected, and all pending transactions have been completed. All CAMT-files has been reproduced and will be delivered again.

The issue that caused all CAMT.53 files received from SDC dated 23/06/2025 to lack the required namespace has been resolved, and the corrected files have been resent.
Should any customers continue to experience related issues—whether with CAMT.53 files or payments—they are encouraged to contact their financial institution for further assistance.

SOLVED 25.06.2025 SDC update has solved the problem with error code 500, and todays CAMT-files contains the xsd information. We awaits a plan from SDC regarding the CAMT-053 with errors.

SOLVED 24.06.2025 Update from SDC: SDC are planning to deploy a fix to night to fix the issues with error code 500.
SOLVED 24.06.2025 CAMT.053 from SDC are missing: xsd:camt.053
SOLVED 24.06.2025 We are still experiencing probkems with requests towards SDC, They are currently returning a 500 error.
SOLVED 23.06.2025 Requests towards SDC are currently returning a 500 error.

SOLVED 20.06.2025 at 6:20 PM: Bank Connect returned 500 errors for all calls from 4:00 pm to 6:20 pm.

SOLVED 16.06.2025 at 12:44 PM: Bank Connect is currently experiencing issues with all calls towards BEC faultstring: 500 OUT message was not received within: 150000 millis.

20.05.2025: Bankdatas bank certificate will be renewed the 20.05.2025 at 10:00 AM. Remember to do a GetBankCertificate, so you always have the newest certificate.

SOLVED 09.05.2025 between 08.05.2025 at 23:45 and 09.05.2025 at 00:20 customers experience timeout.

SOLVED 06.05.2025 - between 06:30 and 10:35 AM: Bank Connect is currently experiencing issues with all calls towards Bankdata failes 633# -- #Unexpected error

SOLVED 06.05.2025 between 04:00 and 08:30 AM: Our test environment is out of order this morning.

SOLVED 05.05.2025 between 10:20 and 11:06 AM: Bank Connect is currently experiencing issues, 500 Internal server error.

SOLVED 28.04.2025 11:30 AM Bankdata are currently experiencing problems processing payments files. The payments files are revives, and will be processed, when the issues are solved.

SOLVED: 27.04.2025 Bank Connect was unavailable from 15:30 to 16:10 and again from 18:00 to 19:00.

SOLVED: 16.10.2024 between 9:44 AM until 10:35 AM We are currently experiencing problems in the test environment.

SOLVED: 08.04.2025 We had problems in the test environment resulting in timeouts.


BEC will renew its intermediate and leaf (BCert) certificates on the April 7th, 2025. Old BEC intermediate and leaf certificates are going to expire April 28th, 2025. If your ERP system utilize the GetBankCertificate request to automatically fetch BEC certificate, then you don't have to do anything.

Otherwise use GetBankCertificate to get the latest certificate.
After April 7th, you will have time until April 28th to switch the BCert certificate used for request encryption. Note that during the period from 7th to 28th BEC will accept, and process requests encrypted with the old BCert, but BEC will sign responses with the new BCert, so it's crucially important that the new BCert is present in your truststore, so that response signature validation doesn't fail.

From now on the BCert lifespan is going to be 2 years, so we urge you to implement automatic certificate retrieval using GetBankCertificate to avoid manual work.

Another important change will be done on April 28th, 2025. The lifespan of customer certificates (KCert) issued by BEC will be reduced from 3 years to 2 years. This change affects only new certificates issued by ActivateServiceAgreement and RenewCustomerCertificate operations. Old non-expired customer certificates with a lifespan of 3 years will be still accepted by BEC.

SOLVED 17.03.2025 in the period from 13:30 - 16:00 - Requests to Bankdata are currently returning: "504# ....#Logningsfejl' in response from bankcentral Bankdata, for EndToEndMessageId: "

SOLVED 12.03.2025 in the period from 11:25 - 11:55 AM we had some networking issues where not all calls got trough to us.

16.02.2025 Scheduled technical adjustments will occur from 2:00 AM to 6:00 AM, causing potential system instability.

21.01.2025 Today at 3 PM we made the announced change regarding Cloudflare. There was a period of around 10 minutres where some requests got a 404 response.

On Tuesday, January 21, 2025 at 3:00 PM, bankconnectservices.dk will migrate to Cloudflare. This will involve a DNS change to a new IP address as well as a new TLS certificate.

pilot.bankconnectservices.dk has already migrated and points to the same production service. This domain can be used to test the connection, DNS resolution, and the new TLS certificate, which is issued by the same certificate authority as the upcoming production certificate.

stest.bankconnect.dk (the test environment) has also been migrated.

SOLVED at 16:50 PM 19.02.2025 Due to some system changes at SDC, there has been a delay in the generation of CAMT-files today. SDC expect the files to be available later in the day.

SOLVED: 09.01.2025 from 13:17 PM and until 10.01.2025 at 2:00 AM, 10% of the calls to Bank Connect get error code 502: ”The remote server returned an error: (502). Bad Gateway”

SOLVED Please be advised that from January 7, 2025, starting at 10:00 PM, until January 9, 2025, at 2:00 AM, there may be some service interruptions due to necessary technical adjustments.

SOLVED 03.01.2025 at 10:45 AM to 11:45 AM Timeouts can be experienced against BEC.

SOLVED 12.12.2024 at 16:00 to 18:45 Currently half of the traffic is getting an error about dns/balancer. We are working on fixing it.

12.12.2024 aT 14:30 Bank Connect installed a new SSL-certificate

SOLVED 06.12.2024 - BEC is currently experiencing major incident that effects Bank Connect application. BEC are investigating the issue, but CAMT053 hasn’t been created yet and BEC are investigation the effect on PAIN.001.

Tests will be conducted from Saturday, 23/11 at 5 PM to Sunday, 24/11 at 10 AM, which may cause temporary service disruptions.

SOLVED 19.11.2024 at 8:27 AM, Requests to SDC are currently returning a 500 error.

SOLVED 15.11.2024 at 17:40 PM, Problems with paymentes at Bankdata

SOLVED 04.11.2024 at 17:45 PM, Some customers calling Bankdata get error code 502: ”The remote server returned an error: (502). Bad Gateway”

SOLVED: 28.10.2024 Between 00.00 AM 27.10.2024 until 09:06 AM 28.10.2024 many customers calling Bankdata got error code 633 “Unexpected error.”

SOLVED: 16.10.2024 between 13:48 until 15:12 We are currently experiencing problems in the test environment.

GetBankCertificate- EndToEndMessageId – max 35 characters. The tag EndToEndMessageId in ServiceHeader has a maximum of 35 characters. But the services GetBankCertificate haven’t in forced it earlier. But since our DNS Configuration Change on Tuesday, August 27, 2024, it is no longer possible to use GetBankCertificate with an EndToEndMessageId longer than 35 characters.

05.10.2024 – Extraordinary service windows at Bankdata from 00:01 AM until 06:00 AM

SOLVED 01.10.2024 Between 10.30 AM until 11.25 AM some customers calling BEC got timeouts

SOLVED 15.09.2024 Between 03.22 AM until 04.10 AM customers calling Bankdata got timeouts and error 504.

SOLVED 11.09.2024 11:32 AM We are currently experiencing network issues, resulting in not all calls getting through to us.

SOLVED 08.09.2024 Between 07.09.2024 kl. 23.23 PM until 08.09.2024 kl. 02:26 AM, BEC had issues with “Straksclearing”, resulting in timeouts.

0SOLVED 04.09.2024 Between 08:20 AM and until 09:15 AM we have had some issues resulting in timeouts.

SOLVED 03.09.2024 Between 08:34 AM and until 08:44 AM we have had some issues resulting in timeouts.

SOLVED 27.08.2024 From 9:30 AM to 10:00 AM, clients attempting to access "bankconnectservices.dk" without preceding it with "www" experienced a 404 error.

Important Notice: DNS Configuration Change on Tuesday, August 27, 2024 On Tuesday, August 27, 2024, we will implement a DNS configuration change, resulting in a new IP address for our service. If you have listed our current IP address in your network configuration (such as in your firewall), you must update your settings to allow our domain, bankconnectservices.dk. You can test connectivity now by accessing https://pilot.bankconnectservices.dk/2019/04/04/?wsdl from your application environment. There has already been a DNS change in our test environment (stest.bankconnect.dk).

SOLVED 21.08.2024 Since Monday customers may have experiences some validations errors regarding signature from BEC. The issue I solved now.

SOLVED 20.08.2024 This morning from about 06:16 - 08:80 we have had some issues with a server, which may have caused timeouts or general instability.

SOLVED 30.06.2024 - 25.06.2024 - Out test environment is currently experiencing some issues. Some calls returns 502 Bad Gateway.

SOLVED 14:15 PM 29.05.2024 - 28.05.2024 - Our test environment are currently experience some issues, you get: "Http/1.1 Service Unavailable"

07.05.2025 - After last weekend weekend, all transactions using Hreg9797 will be rejected.
This means that all ERP Vendors need to change hreg9797 to 9740 when they send in transactions, because Broager Sparekasse and Frøs Sparekasse have merges to form Sydjysk Sparekasse.

SOLVED 23:30 PM 21.05.2024 - Bank Connect is currently experiencing issues with all calls.

SOLVED at 12:40 PM 19.04.2024 - Bank Connect is currently experiencing issues with calls towards BEC: Faultstring 500 Unexpected error. We have received the flowering from BEC:
Between 10:00 AM on April 17th and 03:00 PM on April 19th, BEC will carry out maintenance work on the BankConnect application. The work should not affect the customers.

SOLVED at 15:00 PM 03.04.2024 - Bank Connect is currently experiencing issues resulting in timeouts.

SOLVED at 11:06 AM - 11.03.2024 - Bank Connect is currently experiencing issues with calls towards Bankdata: Faultstring 633 Unexpected error. We're working on a solution.

SOLVED 16.02.2024 Between 20:00 15.02.2024 and until 05:00 16.02.2024 we have had some issues regarding connection to SDC, BEC and Bankdata, resulting in timeouts scr. The issues has been resolved

SOLVED 11:00 AM 27.12.2023 - Bank Connect is currently experiencing issues with calls towards Bankdata.

SOLVED 12:50 PM 03.09.2023 No connection to BEC

SOLVED 18.07.2023 from 20.06.2023 BEC has found a error in RenewCustomerCertificate. It doesn’t return the newest BEC ROOT certifikat, A workaround is to use ActivateServiceAgreement instead,

SOLVED 9:50 AM 07.07.2023 CAMT-files from Bankdata are delayed

SOLVED 25.05.2023 E-conomic have made a changes, so Bank Connect agreements can't be renewed.

SOLVED 21.06.2023 No connection to SDC og BEC from 11:05 AM to 11.58 AM.

SOLVED 15.06.2023 - From 24.05.2023 Some customers (max 10%) using Continia may experiences issues regarding connection to Bank Connect. Bank Connect and Continia are working to fix the problem.

SOLVED 20:25 PM 15.05.2023 from 12:;35 PM Bank Connect is currently experiencing issues with calls towards Bankdata. You get error code 633: "Unexpected error"

SOLVED 11.03.2023 - Bank Connect is currently experiencing issues with calls towards Bankdata.

SOLVED at 14:00 10.03.2023 - Bank Connect is currently experiencing issues with calls towards Bankdata. you get error code 504 Logningsfejl.

SOLVED 08.03.2023 from 00:10 until 04:15, you get error code 504 Logningsfejl in calls towards Bankdata.

SOLVED 07.03.2023 - Bank Connect is currently experiencing issues with calls towards Bankdata.

SOLVED 28.02.2023
28.02.2023 - Bank Connect is currently experiencing issues with calls towards Bankdata.

24.02.2023 Currently timeouts can be experienced against BEC. We are working on finding a root cause and solving the issue.

SOLVED 09.02.2023 - Our test environment isn’t working right now.

SOLVED 18.01.2023 Bank Connect test environment in the morning the 19.01.2023 and until noon, you may experiencing a general instability in the test environment.

SOLVED 17.01.2023 14:30 PM Bankdata - Customer who have activated or renewed certificates since 11.01.2023 and until 14:30 today, may get error code 710.
They have to get a new activations code and generate a new certificate using ActivateServiceAgreement.
Bankdata will contact the banks so they can contact the customers. SOLVED 10:41 AM 17.01.2023 Bankdata, you get error code 710: Certificate validation has failed

SOLVED 13.01.2023 Bankdata - Customer who have activated or renewed certificates since 11.01.2023, may experience problems receiving CAMT and PAINS og deliver payments. They get errorcode 710 - Schema validation failed

SOLVED 12.30 PM 04.01.2023 It is currently not possible to renew and activate customers towards Bankdata