Skip to main content

​
Short answer

Finta keeps your data up to date automatically. The timing depends on how your account is connected.
  • Plaid syncs when the bank reports new activity.
  • GoCardless follows a bank-specific schedule, with no scheduled gap longer than 24 hours.
  • Mercury syncs from webhooks when enabled and hourly otherwise.
  • Stripe syncs after supported Stripe events.
You can also start a manual sync from most destination pages.

​
Sync frequency by provider

The table below covers transaction and provider-record updates. Finta also refreshes account balances once per day; see Daily balance snapshots. On a phone, swipe the table sideways to see all timing details.

​
Daily balance snapshots

Finta refreshes account balances once per day for active connections, regardless of provider. If a destination includes a Balance History table, Finta starts a destination sync after storing that day’s balance snapshot. This balance job is separate from the transaction and provider-record cadences above.

​
Your first sync

Finta begins reading account details after it saves your bank connection. A provider may still be preparing the account list, or the accounts may be ready while their requested data is still arriving. These are different states. The connection’s status chip shows whether the first data sync is pending, partially usable, complete, delayed, or failed. Open the chip to see the available provider-level detail. Plaid can report readiness for individual data types. GoCardless, Mercury, and Stripe do not provide the same product-level evidence, so Finta shows one honest account-data row for those providers. You do not have to wait for the first sync to keep using Finta. Once the saved account is readable, you can select it in destination setup while data is still pending. Finta starts that destination’s first sync after you finish creating the destination. The first sync may take longer than later updates. The provider may still be preparing or returning historical data, especially when you requested a long history or connected several accounts. There is no fixed completion time or client-side countdown.

​
Manual syncs

You can start a manual sync from most destination pages. A manual sync is useful after you:
  • Change a destination’s table configuration
  • Repair its credentials
  • Change its sync start date
  • Fix a setup issue and want to retry
In pass-through mode, a manual destination sync requests fresh data from the bank or provider. Once Storage Mode is fully active, manual syncs serve accounts, transactions, holdings, and investment transactions from Finta’s stored data instead. Neither mode can force a bank or provider to publish data that the provider has not made available yet.

​
Coda syncs

Coda uses Finta Pack sync tables. Start those table syncs from inside your Coda document, not from a Finta destination page.

​
Why data may appear later

An update can arrive later than expected when:
  • The transaction is still pending or the bank has not reported it
  • The provider has not sent an update yet
  • The bank connection needs re-authorization
  • The destination is disabled, has no configured table, or has invalid credentials
  • An initial historical pull or backfill is still running
Check the Syncs page in your Finta dashboard for run history and errors. You can also open the affected connection from the Accounts page or the affected destination from the dashboard to check its status and settings.