Bank connections
Connect eligible institutions through Plaid to bring supported account, balance, and transaction data into OwnCents.
Bank connections · supported data flowSample company
Authorized source
- Eligible account identity and type
- Available and current balance fields where supplied
- Pending and finalized transaction activity
- Supported recurring-stream context
OwnCents records
Common financial context, with the source retained.
Workspace-scoped
A connection is not a promise of every record
Authorization establishes provider access. What OwnCents can actually ingest depends on the configured connector, provider fields and the supported normalization path.
| Supported scope | Not included |
|---|---|
| Normalize supported financial data | Initiate or schedule bank payments |
| Show account and cash context | Guarantee institution coverage or refresh timing |
| Sync pending and finalized activity | Treat provider labels as posted accounting |
Institution support, fields, and refresh timing vary. Bank data is operating evidence and must be mapped and posted through separate accounting controls when accounting authority is required.
From authorization to a useful view
- Choose to connect a bank.
- Complete the institution flow in Plaid Link.
- Select eligible accounts.
- Review normalized data after the first sync.
Questions about Bank connections
Does OwnCents store bank passwords?
No. Institution authentication occurs in Plaid Link; OwnCents does not receive online banking passwords.
Can OwnCents move money?
No. Bank connections are for supported financial data and do not initiate, authorize, transmit, or distribute payments.
Why can balances differ from the bank portal?
Provider refresh timing and institution fields vary. Confirm time-sensitive balances with the financial institution.
Where the information becomes useful
Connect only what the decision needs.
Explore a read-only sample company, or start with your own supported data.