Current operating status of the Bank Connect solution:
Bank Connect is in normal operation
25.05.2023 E-conomic have made a changes, so Bank Connect agreements can't be renewed.
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.
Current information on operations and service windows:
BEC has a new daily service window:
Mon-Fri – 03:00-05:00 AM
Sat-Sun – 04:00-06:00 AM
29.04.2022 New SDC Root CA certificate has been introduced.
Further information under news
Historic information on operations and service windows:
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.
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
SOLVED 00.30 PM 08.12.2022 BEC is back in normal operatin.
SOLVED 5.28 PM 23.11.2022 Bank Connect is currently experiencing issues with calls towards BankData.
SOLVED 8:30AM 28.09.2022 Regarding BEC. You get an faultstring 710 - Schema validation failed. BEC is working om the problem.
SOLVED 02.09.2022 - Our test environment isn’t working right now.
SOLVED 29.06.2022 We have some issues regarding calls against BEC. You sometimes get an error code 500 "Internal server error". BEC I working to fix it.
SOLVED 08.06.2022 We have some issues regarding TransferPayment against SDC.
SOLVED at 13:15 20.05.2022 CAMT and PAIN from Bankdata not delivered since 9:30 AM.
SOLVED at 10:58 AM -12.05.2022 The issues regarding calls against BEC started again. You get an error code 500 "Internal server error". BEC I working to fix it.
SOLVED 12.05.2022 - 06.05.0200 - ActivateServiceAgreement against BEC is not working at the moment. We are working on it.
SOLVED at 15:45 - 11.05.2022 We have some issues regarding calls against BEC. You get an error code 500 "Internal server error". BEC I working to fix it.
SOLVED 11.05.2022 CAMT from Bankdata was delayed this morning. But they were delivered at 8:15 AM.
SOLVED 13:15 - 10.05.2022 We have some issues regarding TransferPayment against SDC. You get an error code 501 regarding MQ problems. SDC I working to fix it.
SOLVED 10.05.2022 CAMT from Bankdata was delayed this morning. But they were delivered at 8:50 AM.
SOLVED 04.05.222 - Jutlander Bank
Jutlander Bank (9217) and Sparekassen Vendsyssel (9070) have been merges to Sparekassen Danmark (9070)
The plan was, that you should be able to use both 9217 and 9070 as mainRegistrationNumber. But an error Bank Connects validation of mainRegistrationNumber has resulted in the fault string 701# … #Identification failed for 9217DK.
This will be fixed by 13:15 today. But you can also changes mainRegistrationNumber from 7217 to 9070, to fix it right away.
We had some issues regarding certificates and a lot of customers got “validation has failed”
If you still get errors regarding certificates, try to make a RenewCustomerCertificate, of write to us for at new activations code for ActivateServiceAgreement.
SOLVED 25.04.2022 - Our test environment is still not working, Users will experience timeout og fault 710 Certificate validation has failed.
We are working to solve the problem. We will send out a new status tomorrow.
SOLVED 19.04.2022 - Our test environment isn’t working right now.
We are experiencing pro BEC are investigated it right now.
blems towards BEC.
SOLVED Fen 6th 2022
Periodic problems between 6:00 – 5:30 AM
SOLVED Jan 23th 2022
Periodic problems against Bankdata between 9:00 – 12:30
SOLVED Jan 18th 2022
Periodic problems against Bankdata between 12:30 – 13:30
The issue was caused by an increased load in BEC's. The issue was not directly related with Bank Connect.
We are experiencing timeouts towards BEC. The problem is being investigated.
BEC suffered a major outage during the night of October 12, which delayed batch generation up to 4-5 hours. It is possible that some CAMT files are marked as sent from BEC, however the ERP house has timed out after 2-3 minutes on the request. This means those files were not transmitted further down the chain. The only available solution to missing CAMT files is to ask customers to reorder the missing files through their bank adviser, after which the missing files can be downloaded again from BEC.
SOLVED october 12th. 2021
BEC is sometimes experiencing problems returning CAMT-files with a lot of data. The cause is an infrastructure component in the network.
BEC is investigating the issue.
SOLVED october 1th. 2021
Bank Connect test enviorment
We are experiencing a general instability in the test environment at the moment.
SOLVED june 24th. 2021
Setup and handling of connections has been changed in a firewall update.
This has coursed periodic errors, if an ERP-provider has used the same connection several times In the same request.
SOLVED may 19th. 2021
There have since 11.20 am been Unstable operation against Bankdata. Bankdata is working on a solution and expects normal operation later today.
SOLVED April 9th. 2021
If you use the operation GetStatus you can experience timeouts,
When you try to pick up Pain.002 files from BEC.
SOLVED April 8th. 2021
Time-outs can currently be experienced against SDC,
this can also affect the other data centers.
SOLVED March 30th 2021 Time-outs can currently be experienced against SDC,
this can also affect the other data centers.
We're working on a solution. SOLVED March 15th. 2021
Timeout against SDC can currently be experienced
SOLVED March 8th. 2021
Unstable operation may currently be experienced
SOLVED Febuary 9th. 2021
There is heavy load on the servers at BEC and response times, timeouts and errors can be experienced.
SOLVED Jan 4th 2021
Dec. 21st. - The Bank Connect test system is currently out of order
SOLVED All FI-notification is now done
Dec. 17th. 2020 - 9.00AM
CAMT.054 FI-notifications are delayed for Bankdata banks
SOLVED! Monday 26th of October
Since sunday night, we have had some issues with one of our servers, which prevented Bank Connect from having a stable system. Right now the server has been closed, while being fixed, and the system is running stable.
We are working on a solution to restore normal operation.
If you a are experiencing any errors, you should try to make the call again.
SOLVED! Thusday 14. th of july
There may currently be periodic problems against BEC
BEC is working on the problem.
Friday 10. th of july
SDC has a service window on Sunday, 12-07-2020. It is a normal monthly technical service window on the infrastructure.
This can cause brief periods of instability between 2 am to 5 am.
Thursday 11.th of June 2020 - 3 pm.
BEC has now sucessfully changed their Bank Certificate.
If any costumers are experiencing any certificate errors,
call getBankCertificate, this solves the problem.
If this is not an option, please refer your customer to the bank advisor who can order a new activation code for Bank Connect
From 5 am until 6 am all systems will be down for maintenance and no transactions will be processed in that period..
Thursday 11.th of June 2020 SOLVED!
BEC has changed their Bank certificate
BEC does still have problems with their new Bank certificate
BEC are in progress with fixing the problem
New status 14 pm.
June 9th SOLVED! Production Problems at BEC, when changing the bankcertificate
June 2nd SOLVED!
We are experiencing problems with our test environment
We are working to resolve the issue as soon as possible
Operational Problems toward BEC
May 19th. at 10.00 am
Extended response times and interruptions toward BEC.
BEC is working on a solution
New status at 16.00 pm
*SDC has an extraordinary service window on Sunday, 17-05-2020 between 2 am and 6 am. This may cause brief periods with instability between 3:15 am to 3:45 am
We are experiencing problems with our test environment, which is currently unavailable.
We are working to resolve the issue as soon as possible.
May 4th. we experienced problems with a change of certificate at SDC datacenter
The problem was solved at 3.45PM
May 4th. 2020 kl.11.20AM
SDC has put on a new certificate
New update as soon as it works.
May 4th 2020 9.30AM
SDC are working on the problem.
Update at 11AM
May 4th 2020 - 8.AM
We are experiencing problems with SDC.
Update at 9.30.AM
Tuesday april 21st There are currently challenges in obtaining bank statements from SDC. We are working to solve the problem. New update no later than 10 am.
Tuesday april 7th - update 11.55 SDC made a rollback
Operation problems can be seen
We are working to find cause and solution.
New update no later than 12 o'clock
Wednesday, March 25th 2020
Bankdata has created and delivered the missing CAMT files.
Wednesday, March 25th 2020
Bankdata are currently experiencing problems creating CAMT files
SDC - missing CustomerStatement.
SDC are currently investigating some issues regarding missing CustomerStatement.
March 5th 2020
We need to renew an internal certificate. Between 22:00 – 24:00 Thursday evening users might experience at short down time, expected duration less than one minute.
Fridag 22th of Nov 2019 from 11.05 am to 11.20 pm.
Some customers got a timeout.
Update Nov. 22th 2019 The servers was not running and the costumers got a timeout. Update okt. 10th 2019 BankConnect is up and running. Update okt. 9th 2019 Bankdata is currently having trouble processing payments. Bankdata receives all deliveries, but deliveries larger(over 800kb) and deliveries containing payments to NemKonto are received and will be processed later. We will not send any Pain.002 receipts on received deliveries, they will be done later. The duplicate control will ensure that your deliveries are not processed multiple times. CAMT.054 extracts for delivery during the day are also not formed
Update Sept. 12th 2019 We believe now to have found the problem. We are initiating a change tonight which should solve the problem. New update on sept. 13th 2019 Sept.11th 2019 We are currently experiencing issues with certificates on Bankdata. We have experienced that new certificates can cause problems and suppose that also renewal of already excisting cetificates can cause errors too. We are investigating the problem. An update on the problem will be made no later than Thursday the 12th of september at noon
Monday 26th of Aug 2019 from 11.30 am to 12.30 pm.
Some customers got a timeout.
Thursday 27th of June 2019
The servers was not running and the costumers got a timeout.
Wednesday, May 8th. 2019.
Bankdata has stated that there are problems with the automatic user authentication of submitted payments. However, customers can manually authenticate for payments in the bank. Friday, February 1st. 2019.
Bankdata is currently having problems, which can cause challenges for customers at this data center. We will provide update as soon as the system is back up and running.
Tuesday , Januar 8th 2019
Some customers got the message: "Could not create SSL / TLS secure channel". This was due to an unannounced upgrade of TLSv1.0 to TLSv1.2. The problem occured from 8.20 AM to 9.30 AM.
Thursday, September 20th. 2018,
TLSv1.2 was downgraded to TLSv1.0 and the solution was functioning for all costumers Again. The upgrade to TLSv1.2 is now announced for launch on Monday, February 11th. After this date it is no longer possible to use TLSv1.0 and v1.1 against Bank Connect.
Wednesday, September 19th. 2018
Some customers got this message: "Could not create SSL / TLS secure channel". This was due to an unannounced upgrade of TLSv1.0 to TLSv1.2.