Is finAPI Live Down Right Now? Check if there is a current outage ongoing.

Unfortunately, due to a technical adjustment at the bank and finAPI, the connection is not possible at the moment. Updates can also run into errors. We are working with the bank to re-establish the connection and will keep you updated.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Sehr geehrte Damen und Herren,aufgrund von Wartungsarbeiten in den kommenden zwei Wochen wird es zu Beeinträchtigungen auf den von Ihnen verwendeten Schnittstellen kommen.• Di, 3.6. 22 Uhr - Mi. 4.6. 4 Uhr• Do, 5.6. 22 Uhr - Fr. 6.6. 4 Uhr• Di, 10.6. 22 Uhr - Mi. 11.6. 4 UhrBitte berücksichtigen Sie dies während des Wartungsfensters in Ihrem Monitoring.Sollten unsere Wartungsarbeiten frühzeitig abgeschlossen sein, werden wir Sie informieren.Mit freundlichen GrüßenIhre DKB AG---------------------------------------------------------------------------------------------Dear Sir or Madam ,we have scheduled 3 maintenance windows in the coming two weeks: • Tuesday to Wednesday, 03.-04.06.2025 22:00 – 04:00• Thursday to Friday, 05.-06.06.2025 22:00 – 04:00• Tuesday to Wednesday 10.-11.06.2025 22:00 – 04:00DKB will undergo a complete downtime at the above times, please take this into account in your monitoring.If the maintenance is completed early, we will inform you.Best regards,Your DKB AG

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dear Customers,A new finAPI version will be released.For your information:Maintenance windows for all finAPI environments (Live, Sandbox) are scheduled every Wednesday 10:00 pm - Thursday 03:00 amAlthough we are working hard to avoid downtimes, short downtimes can be expected in these scheduled maintenance windows.Best Regards,Your finAPI team

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Postbank and Norisbank perform large scale maintenance and migration work on the weekend 23.05. - 25.05.2025, which will result in transaction retrieval and payment submission for both banks not being possible.--------The migration will result in the APIs not being available for the following time periods –Norisbank – Friday 23rd May, 2025 from 17:00 CEST till Sunday 25th May, 2025 evening. Postbank – Saturday 24th May, 2025 from 04:00am CEST till Sunday 25th May, 2025 evening.Sincerely,Your Deutsche Bank XS2A-Team

We have updated the scraper to resolve CAPTCHA issues.

American Express is actively trying to block our webscraper again. Imports and updates currently might fail. We're looking into how to modify the webscraper to avoid getting blocked and will keep you posted.

In recent days, there has been an increase in phishing emails containing fake tax notifications – allegedly sent on behalf of the German Federal Central Tax Office (BZSt). These messages urge recipients to settle an “outstanding tax payment”. The included link leads to a fake website featuring a deceptively authentic-looking finAPI payment form. Further information can be found under the following link: https://www.finapi.io/en/finapi-informs-caution-phishing-attempts/

We see an issue with the connection with Union Investment accounts via scraper We are already working on it and will keep you updated.

This incident has been resolved.

We see an issue with the connection with FIL Fondsbank accounts via scraper. We are already working on it and will keep you updated.

We see an issue with the connection with Union Investment accounts via scraperWe are already working on it and will keep you updated.

Together with the service provider from Finom and Swan, we could solve the problem.

Currently for Finom and Swan payment submission and account information retrieval fail with error message "Given certificate could not be found.". We are already in contact with Finom and Swan technical team to resolve this issue. We'll keep you posted.

We just deployed the fix for the webform, and it workes regularly now. Please excuse the inconvenience

We are currently preparing a solution. We will inform you as soon as it goes live.

We detected an incorrect resource handling on the server side while loading the embedded web form. We are currently working on it and inf

This incident has been resolved.

apoBank currently has massive problems with its FinTS server and has deactivated it, please see https://www.apobank.de/unsere-leistungen/konto-karte/online-banking/status-online-banking The deactivation of FinTS also broke the XS2A service. Current notice The FinTS interface has been temporarily deactivated due to a technical fault. As a result, there are interruptions in the use of the FinTS service. We are working hard to rectify the problem. apoBank is working on the problem, solution horizon still unclear.

This incident has been resolved.

American Express is actively trying to block our webscraper yet again. Imports and updates currently might fail. We're looking into how to modify the webscraper to avoid getting blocked and will keep you posted.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Starting on Wed. 19.02.2025 after 10 pm we see an increased number of bank connection imports, updates and payment submissions fail with the error message ""User PSU-* header is required for the operation, but none was given"". Our technical team is already investigating the root cause of this issue. We'll keep you posted.

A new version of the Miles & More web scraper, that fixes the issue, was released on 03.02.2025.

Connecting to Miles & More accounts via Webscraper is currently not working. We are already investigating the error.

A new version of the Amex webscraper aiming to resolve issues was released on 22.01.2025.

Unfortunately, the import and update of AMEX connections is not working at the moment. The error message says that the access data is incorrect, although it is correct and users can log in to their online banking with it. We are working on a solution and will keep you informed.

The bank has fixed the issue.

DKB has reported a general connection problem. The bank is working on a solution and we will keep you informed.

The disruption has been fixed and the server is working again.

We are currently facing technical issues with DKB XS2A Connections. Together with the bank, we are working on a solution with high priority.

At the moment we are not seeing any major errors at Trade Republic, but we will continue to monitor this.

Trade Republic is increasingly blocking our IPs for the retrieval of account information. We have contacted Trade Republic about this and hope to find a solution soon.

This incident has been resolved.

On 12.09.2024 Finom introduced a bug on their side, which broke our integration with them. Imports, updates and payments are currently not possible as a result. We already reached out to Finom asking them to fix the problem they introduced. They confirmed the are already working on a solution. We'll keep you posted.

We released an adjustment proposed by the bank which fixed the issue.

Recently Revolut introduced a change, which broke our Revolut integration. Imports, updates and payments are currently not possible as a result. We already reached out to Revolut asking them to fix the problem they introduced. We'll keep you posted.

We see in our log that the error has been fixed by the bank since last Friday.

The bank has informed us that a fix for the error will be released this Sunday (01/09/2024).

We are currently facing technical issues with FNZ XS2A Connections. The bank is already informed and working with high priority on a fix. We are monitoring the situation and will keep you posted.

The error was fixed by the bank at around 14:30. Retrieval is now successful again.

DKB is experiencing disruptions since Saturday afternoon, causing account retrieval to fail. The bank is already working on a solution with high priority.

We released a fix yesterday evening for this issue. Please do not hesitate to contact us if you encounter any problems.

We see an issue with the connection with apoBank accounts via XS2A. We are already working on a fix and will, of course, keep you up to date.

After we have been making continuous improvements to the scraper recently and are currently seeing stable operation.

With yesterday's release, we have made a few adjustments to the Amex scraper live. We can see in our logs that the success rate has gone up and hope that we stay on this level. Unfortunately, we also see that it does not work for all accounts and not consistently and that users may have to try more often. Nevertheless, we are still trying to get in touch with Amex.

Unfortunately, the adjustments at the scraper only helped users with the update until captchas were displayed. We have now contacted Amex and are trying to find a solution together.

American Express introduced again new changes to their website, preventing our webscraper from working properly. Imports and updates might fail at the moment. We are working on adjusting our webscraper and aiming to release the adjusted webscraper as soon as possible, We'll keep you posted.

This incident has been resolved.

American Express apparently introduced new changes to their website, which prevent our webscraper from working properly. Imports and updates might fail at the moment. We are working on adjusting our webscraper and aiming to release the adjusted webscraper as soon as possible, We'll keep you posted.

After the recent release of an adjusted American Express webscraper imports and updates are working properly again.

American Express introduced changes to their website, which prevent our webscraper from working properly. Imports and updates might fail at the moment. We are working on adjusting our webscraper and aiming to release the adjusted webscraper as soon as possible, We'll keep you posted.

This incident has been resolved.

Resulting from changes on the bank side on March 17, 2024, collective money transfers submitted to UniCredit/Hypovereinsbank via our API are currently failing. Single money transfers as well as single and collective direct debits are not affected. We are working hard to resolve the problem as soon as possible. Updates to follow.

According to Atruvia the issue is resolved.

Currently VR-Banken/Geno seem to experience technical issues on their side, which affect the availability of the interfaces. Imports, updates and payments for VR-Banken might fail currently. We reached out to the bank group's support team and keep you posted.

This incident has been resolved.

If you are pinning ssl certificates from your side or are manually managing your truststore, please check the finapi sandbox connection. As we will be replacing the SSL certificate this Saturday for finapi live, please contact us today if you have not already done so. The pinning can cause issues with the connection. On Sandbox, the new certificate is already set. So if your handling of sandbox is equal to live and you see no issues, everything is fine. Please write to us at support@finapi.io with the subject "SSL certificate"

As previously announced, during the release of finAPI Access 2023.46.1 we have successfully removed all N26 transactions that were delivered by N26 with an incorrect amount sign. The affected bank connections have been prepared to enforce transactions download for an extended time period during the next manual bank connection update or batch update, to correctly restore the transaction history. Please note that this might trigger a new SCA for your users to issue a new consent for the affected bank connections. If a user imported a bank connection during the time when N26 delivered transactions with wrong signs, all transactions have been deleted, as all were affected by the N26 issue. For such bank connections, a maximum of 90 days will be downloaded.

To fix the transactions that have been delivered by the bank with an incorrect sign, we plan to delete them from all N26 accounts, that have been updated in the timeframe, in which the bank delivered them incorrectly. The bank released the bug on October 25th. To be sure we get all broken transactions, we plan to delete N26 transactions that have been imported since October 24th with the next release tomorrow evening. Since the bank has fixed the issue, the next update of these affected accounts will re-import the deleted transactions correctly.

We see issues with the connection to the bank server of N26 and with a wrong sign at the transaction. We have already contacted the bank and are waiting for feedback.

Schufa fixed the issue on their side.

Schufa informed us about technical problems of their application. This can cause problems with finAPI products connected to Schufa.

Due to issues at DKB's data center, there were some disruptions yesterday. The connection should now work again.

DKB Deutsche Kredit Bank XS2A and webscraper interface connection failing because of an error on the banks side. The bank is working on a solution.

The IT service provider of the banks informed us that the server is running stable again. If you still have problems with the connection, please contact us.

We are currently facing technical issues with Oberbank, BTV and BKS XS2A Connections. The bank is already working with high priority on a fix. We are monitoring the situation and will keep you posted.

We see only a few processing errors left and will inform the affected customers separately if necessary. We wish you a nice weekend!

We see issues with the connection with the server of Schufa. This can cause problems with finAPI products connected to Schufa.

The outage is fixed.

We are currently facing technical issues with Oberbank, BTV and BKS XS2A Connections. The bank is already informed and working with high priority on a fix. We are monitoring the situation and will keep you posted.

This incident has been resolved.

We are currently facing technical issues with OLB XS2A Connections. The bank is already informed and working with high priority on a fix. We are monitoring the situation and will keep you posted.

This incident has been resolved.

Currently we are facing problems connecting to Erste Bank / Sparkasse Austria banks. No imports, updates or payments are possible. We are already working with Sparkasse Austria's PSD2 XS2A team to resolve the issue. We'll keep you posted.

This incident has been resolved.

Another change on the Scalable Capital website is currently impairing data download. Imports and updates fail. We are already working on adjusting our webscraper and aim to release the new webscraper asap. We'll keep you posted.

This incident has been resolved.

A change on the Scalable Capital website is currently impairing data download. Updates fail. We are already working on adjusting our webscraper and aim to release the new webscraper asap. We'll keep you posted.

This incident has been resolved.

Due to some changes at the online banking of Scalable Capital, the scraper connection is failing at the moment. We are already working on a fix and keep you updated.

We are happy to inform you, that ING fixed the issue yesterday evening.

We see an issue at the connection with ING Bank accounts via XS2A. We have already contacted the bank and they informed us that they are currently working on highest priority to resolve this. When we have more information we will share this right away.

Commerzbank announced the technical issue has been resolved.

Currently Commerzbank is facing a general outage of its PSD2 XS2A services as reported here: https://psd2.developer.commerzbank.com/news As a result transaction retrieval and payments are not possible. We are monitoring the situation and will keep you posted.

Commerzbank has solved the issue.

Currently Commerzbank is facing a general outage of its PSD2 XS2A services as reported here: https://psd2.developer.commerzbank.com/news As a result transaction retrieval and payments are not possible. We are monitoring the situation and will keep you posted.

XS2A connection is available again

Atruvia XS2A Connections are currently not possible due to technical problems. We are already analyzing the problem with high priority. We´ll keep you posted.

This incident has been resolved.

Due to changes made by Trade Republic on their homepage, currently all webscraper services fail. We are working with high pressure on adjusting the web scraper to provide our customers with an updated scraper as soon as possible. We'll keep you posted.

This incident has been resolved.

Dear customers, due to a breaking change introduced by N26 regarding their payment service, we temporarily have to switch off the payments services for N26 accounts. As soon as we have a solution, we'll inform you immediately. We expect to fix it again with tomorrow's release so that the payment services can continue. Best Regards, Your finAPI Team

The scraper has been updated in the meantime. If you still encounter problems, please feel free to contact us.

We see an issue with the connection with Fil Fondsbank accounts. The bank has enabled the address verification for all users. We are checking how we can skip it with the scraper, but currently, the scraper fails due to the unexpected page. Users can fix it by logging in once manually to their Online banking and approving their address data.

Just recently we released the adjusted version of the webscraper.

Scalable Capital recently introduced changes to their website, which broke our webscraper implementation. Currently no new transactions and security positions can be downloaded. We are currently already working on adjusting our webscraper to the introduces changes and plan to release the new webscraper asap. We keep you posted.

Trade Republic fixed the issue with SEPA payment deposits in the broker. If you still detect issues with users' accounts, please contact us.

Unfortunately, at the moment we see some issues at the online banking of Trade Republic. The details of an amount transferred to the account are not displayed correctly, which currently leads to an error of the scraper.

This incident has been resolved.

Imports via the Smartbroker web scraper interface are currently failing as users are required to consent to the new prices, terms and conditions. We are adjusting the interface to handle this scenario in the upcoming release. In the meantime, users may consent to the changes in the broker to circumvent the error.

Issue fixed by the bank.

Currently we are facing issues to connect to Raiffeisen Austria. Account information services and payment initiation services are not possible. We reported the issue to Raiffeisen Austria's technical supplier already and are currently waiting for a fix of the issue on the bank side. We'll keep you posted.

The adjusted Scalable Capital webscraper was released with Access version 2023.03.3.

Scalable Capital introduced changes to their online banking, which broke our webscraper implementation. Currently attempts to fetch new transactions and securities from Scalable Capital fail. We are already adjusting our webscraper to the changes and will release the new version of the webscraper asap. We'll keep you posted.

We've re-enabled the Postbank scraper with the last release. Since the IBANs for non-payment accounts were changed, all previously imported non-payment accounts will have the status DEPRECATED when updating the bank connection. Credit card accounts are not expected at this time as they have not been migrated yet. In line with the banking portal's login flow, the scraper will no longer return a TSP selection list and will trigger SCA on the user's default device.

We are reimplementing the web scraper to continue our AIS Services for non-payment accounts as soon as possible.

Due to the bigger changes on the website of Postbank, we have to temporarily disable the Postbank scraper. This effects non payment accounts (AIS) . We do this to prevent users from locking their bank accounts caused by error messages we get from the bank regarding wrong credentials.

The XS2A service provider of DKB informed us today that they released a fix for the current issue and the service should now run again. From our side we can confirm that and we hope you and your users have the same experience. However, if you encounter any problems, please contact us.

DKB is investigating this issue and tries to add a workaround until they fix the issue.

Dear customers, unfortunately, we have to inform you, that there are again it again to errors at the XS2A interface of DKB. We will pass on more information about this as soon as we have a response from the bank.