Stability and consistency of Open Finance integration (Bradesco)

I would like to make a suggestion for improvement related to Open Finance integration with Banco Bradesco, as I have been experiencing recurring operational problems that directly impact the reliability of financial monitoring.

Currently, the connection is frequently unstable, with episodes of:

duplicate transactions after synchronizations;

transactions that are not imported (mainly PIX);

excessive delays in updates.

This behavior indicates possible failures in consent continuity, in the incremental synchronization process, or in the transaction deduplication logic during data ingestion.

As a suggestion for improvement, it would be extremely relevant to:

• improve the incremental synchronization mechanism, ensuring consistency between the bank statement and the imported data;

• implement an automatic reconciliation process capable of identifying gaps and reprocessing unsynchronized periods;

• improve the deduplication logic, preventing the same transaction from being entered more than once;

• provide a clear connection status indicator (last successful synchronization, need for reauthorization, consent failure, etc.);

• allow, if possible, a forced synchronization action with controlled historical reprocessing, without the need to delete and reconnect the account.

Today, slow updates and import inconsistencies mean that users cannot fully trust the balance and history presented in the application, which significantly reduces the value of Open Finance integration in everyday use.

I understand that Open Finance integrations involve external dependencies and limitations of the bank itself, but improvements in the reconciliation layer, connection observability, and inconsistency handling would make a very significant difference in the experience.