Connect your bank via Plaid with Zensus

Bank transactions, account balances, and account names with the last four digits of each account number, for every institution you connect through Plaid. Zensus also reads the institution's name, so you can tell your accounts apart.

Your bank password, your full account number, or your routing number. Zensus asks Plaid for one product, Transactions. It does not ask for Plaid's Auth or Identity products, which are the ones that return account numbers and account-holder details. You enter your bank login in Plaid's window, and it never reaches Zensus.

Your balances are the cash your forecast starts from, and your transactions show the money that has actually moved. Both come straight from the bank, not from a spreadsheet export, so the date your cash is projected to run out rests on what has cleared.

1. In Zensus, open Settings, then Integrations, and choose to connect a bank.
2. Plaid opens in its own window. Pick your bank and sign in there.
3. Plaid hands Zensus an access token. Zensus stores it encrypted with AES-256-GCM and runs the first sync.

Plaid notifies Zensus by webhook when new transactions are ready, and Zensus syncs then. A daily sync runs as a fallback. Zensus also refreshes when you open the app if the data is more than an hour old, and you can press Sync at any time. How soon a transaction appears depends on when your bank reports it to Plaid.

Open Settings, then Integrations, and disconnect the bank. Zensus asks Plaid to remove the connection, which ends its access. It deletes the stored access token and the synced bank transactions right away.

The Plaid access token is encrypted at rest with AES-256-GCM. Zensus never stores bank credentials. The connection is read-only: Zensus reads transactions and balances and cannot move money.