Your Data's Journey
From consent to destination - here's exactly what happens during a BankSync sync.
“For pass-through syncs, your data flows to the destination you choose. For managed features, it stays inside the BankSync Boundary until you send it elsewhere.”
Consent & Authentication
You authenticate with your bank through the licensed provider's hosted consent interface. BankSync never handles your banking credentials. Authentication happens directly between you and your bank.
Technical detail: The licensed provider for your region (listed on our provider disclosure pages) issues a tokenised connection. Only this token (not your credentials) is stored by BankSync, encrypted at rest.
Sync Request Triggered
A sync is initiated, either on a schedule you configure or on demand. BankSync dispatches a sync job to an edge worker.
Technical detail: The sync runs as a Cloudflare Workflow. The request handlers that start and schedule it are placed in the United States (Google Cloud us-central1); the Workflow's steps run on Cloudflare's global network, and their checkpoints are held in Cloudflare's globally distributed durable storage for the life of the run, not pinned to one region. Server-side calls to Quiltt (MX and Finicity connections) leave from BankSync infrastructure in the United States, which Quiltt requires for CFPB Section 1033 data residency.
Data Retrieval
The edge worker calls the licensed provider's API using your stored access token to retrieve the requested financial data (transactions, balances, or holdings). Licensed providers such as Plaid, Salt Edge, Fiskil, and future open banking providers may operate under their own terms, controls, regulatory obligations, and security practices.
Technical detail: The licensed provider authenticates the request, applies your consent scope, and returns only the data categories you have authorised. Data is received into the sync step and checkpointed by the workflow engine for the life of the run.
Transform & Forward
The edge worker applies your configured field mappings and transformations, then writes the data to your connected destination. That destination may be a customer-selected third-party tool or a BankSync-managed feature such as future BankSync Tables.
Technical detail: Pass-through destination data is not retained after the write completes. Data written to a BankSync-managed feature remains inside the BankSync Boundary until you delete, export, share, sync, or otherwise send it outside that boundary.
Completion & Audit Log
The sync job completes. BankSync records only operational metadata (timestamps, record counts, and any errors), except where data is stored in a BankSync-managed feature you enabled.
Technical detail: The audit log tells you when syncs ran and whether they succeeded. This metadata is used to power your sync history view and to self-heal any failed sync jobs. Managed feature content follows the retention and access controls for that feature.
Ready to Sync Your Accounts?
Connect your bank and start syncing in minutes.
- No credentials stored
- Read-only access
- Pass-through architecture