Allow users to connect their own SimpleFIN Bridge account to sync read-only bank transactions. Each user manages their own connection from the Data page — no bank credentials are stored.
Allow users to connect SimpleFIN
When enabled, users see a Bank Sync section on their Data page.
Auto-sync interval
How often the background worker checks for new transactions.
Sync lookback windows
SimpleFIN uses two different windows depending on sync type.
Initial connect & backfill
{seedDays} daysThe first sync (and any manual backfill) fetches up to {seedDays} days of history to build a complete transaction picture. This is fixed — SimpleFIN Bridge enforces a strict {maxDays}-day hard limit, so this stays one day under it to avoid latency-related errors.
Routine sync lookback
How far back each auto-sync and manual "Sync Now" looks after the initial connect. Recommended: 7–30 days. Setting this near 45 increases request size and duplicate-skip work with no benefit once history is established.
{maxDays} days is SimpleFIN Bridge's maximum. Requests at this limit may occasionally fail due to request latency — 30 days or less is recommended for reliable routine syncs.
Auto-sync worker
Status
{worker.running ? 'Running' : 'Idle'}
Last run
{worker.last_run_at ? timeAgo(worker.last_run_at) : '—'}
Next run
{worker.next_run_at ? `in ${timeUntil(worker.next_run_at)}` : '—'}
{config?.encryption_key_source === 'env'
? <>SimpleFIN credentials are encrypted at rest. Encryption key is loaded from TOKEN_ENCRYPTION_KEY — stored separately from the database, so a database backup alone cannot decrypt credentials.>
: <>SimpleFIN credentials are encrypted, but the key is stored in the same database as the data. A database backup or file-level read includes everything needed to decrypt credentials. Set TOKEN_ENCRYPTION_KEY in your environment to keep the key separate.>
}{' '}
Regular database backups preserve all user connections.