Plaid
Use Plaid Link to connect eligible institutions and normalize supported account, balance, transaction, and recurring data.
Plaid · supported data flowSample company
Authorized source
- Eligible institution and account metadata
- Supported balance fields
- Pending and finalized transactions
- Supported recurring transaction streams
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 |
|---|---|
| Connect supported institutions | Receive online banking passwords |
| Synchronize supported financial records | Initiate ACH, wire, or card payments |
| Normalize provider fields into canonical OwnCents models | Guarantee institution uptime or data completeness |
Institution coverage, provider fields, balances, and refresh timing vary. OwnCents never uses Plaid to initiate or distribute payments.
From authorization to a useful view
- Open Plaid Link from an authorized workspace.
- Authenticate with an eligible institution.
- Choose supported accounts.
- Allow the bounded server-side sync to normalize records.
Questions about Plaid
Who handles institution login?
Plaid Link handles the institution authentication experience; OwnCents does not receive the online banking password.
How quickly does data refresh?
Timing depends on Plaid and the institution, so time-sensitive data should be confirmed at the source.
Can Plaid data post to the ledger automatically?
No. Normalized operating data and controlled accounting posting are separate workflows.
Where the information becomes useful
Connect only what the decision needs.
Explore a read-only sample company, or start with your own supported data.