@PhilippeF#233207

Hi Philippe,

Can you please tell me the exact steps you follow and do you get any error? This way we will have better insight, so that we can help you accordingly 🙏

Bij komen (ook vanaf vrijdag) transacties in Exact Online niet meer binnen.

@fonql-Silver-Llama#233245 Vervolg: het gaat om automatische koppeling die sinds het begin altijd feilloos heeft gewerkt. Geen foutmeldingen, logboek tot vrijdag normaal daarna niets meer

Hello bunqers 👋

We have escalated this as a bug to our developers team, and we will let you know once it's fixed 🙌

For now I wish you a great day ahead 🌈

I'm happy to tell you this has been fixed now! Let us know if you keep having any issues and we'll check further 👍

What about fixing the missing transactions? What is status?

@Frederik-Violet-Badger#233379 bunq won't send notifications for old transactions and no actual transaction data has been affected in the first place. The third-party app can and should always get all past transactions that weren't synced properly by calling the respective API endpoints themselves. If they don't do that, then you would probably have to do it manually or by importing an account statement if that's supported by your app.

Relying solely on the callbacks/webhooks (what broke last weekend) isn't a great idea. Not sure if anybody does that, but if your third-party app seems to be doing this, the quality for their bunq integration should be called into question. After all, even if rare, outages can always happen. Not just at bunq, but also for the third-party app itself. The callbacks are "nice to have", but they're just one part of an integration. If that's all an app uses, they're asking for trouble. Most banks don't even offer them.