OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 7.5/10
Structured API for the declared product scope
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
The declared Transactions product exposes normalized financial-account transactions.
Transactions API reference ↗
Transactions; /transactions/sync · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Iterate up to 500 updates per page; initial history is bounded by account/product availability.
Transactions API reference ↗
/transactions/sync > count; cursor; next_cursor; has_more · Checked 2026-10-16
Query expressiveness 8.8/10
Documented structured API filters
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Date and account selection are documented; API records are not live bank SQL.
Transactions API reference ↗
/transactions/get > start_date; end_date; options · Checked 2026-10-16
Access cost barrier -
-
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
Plaid Quickstart ↗
Introduction > API Key; How it works; Making API requests · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility 5.0/10
Separate provider consent or partner agreement required
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Full production product access requires application; some institutions also require OAuth registration.
Sandbox and limited production ↗
Limited Production · Checked 2026-10-16
Downstream permission -
-
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
Plaid Quickstart ↗
Introduction > API Key; How it works; Making API requests · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface -
-
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Assessed endpoints read or refresh bank data; sandbox creation does not establish production mutation rights.
Transactions API reference ↗
Transactions > Endpoints; See also · Checked 2026-10-16
Custom application path 5.0/10
Approved third-party applications using fixed interfaces
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Custom apps use Plaid APIs, with separate production product and institution eligibility.
Plaid Quickstart ↗
Get started with the Quickstart; Introduction · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 7.5/10
Documented updated-since filters or webhooks
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Poll scoped cursors after update webhooks; this is an API change feed, not source-bank database CDC.
Transactions API reference ↗
/transactions/sync; SYNC_UPDATES_AVAILABLE · Checked 2026-10-16
Limit visibility 10.0/10
Published numeric quotas and recovery instructions
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Numeric per-Item and per-client limits and rate-limit error handling are published.
Rate Limit Exceeded errors ↗
Transactions endpoints; Troubleshooting steps · Checked 2026-10-16
CDC and deletion capture 7.5/10
Updates and deletion identities documented for the stated resources
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Sync returns additions, modifications and transaction removal identities for the selected Item/account stream.
Transactions API reference ↗
/transactions/sync > added; modified; removed · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Saved cursors resume updates; an eligible empty-cursor request can rebuild available Item history. For TRANSACTIONS_SYNC_ITEM_LIMIT_EXCEEDED, keep the saved cursor: an empty-cursor restart is prohibited. Use /transactions/get or contact Plaid Support when the supported cursor path cannot continue. No retained replay guarantee is inferred.
Transactions API reference ↗
/transactions/sync > cursor; count; Pagination instructions · Checked 2026-10-16
Transactions errors ↗
TRANSACTIONS_SYNC_ITEM_LIMIT_EXCEEDED · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
The application receives structured records and removed transaction IDs.
Transactions API reference ↗
/transactions/sync > added; modified; removed · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
A customer cancellation retrieval window and any exit charges have not been established.
Plaid Quickstart ↗
Introduction > API Key; How it works; Making API requests · Checked 2026-10-16
Planned migration fidelity 7.5/10
Portable structured records on documented routes; whole-product completeness unverified
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Portable transaction records are established within supported accounts and available history, not source-bank completeness.
Transactions API reference ↗
Transactions; /transactions/get · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Developers run their own integration code; native workflow artifact rights remain unresolved.
Plaid Quickstart ↗
Quickstart setup; How it works · Checked 2026-10-16
Rights to custom logic -
-
Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Plaid Quickstart ↗
Introduction > API Key; How it works; Making API requests · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
An application team obtains a client ID and environment-specific secret from the Plaid Dashboard. Link exchanges a public token for a persistent Item access token after the user connects an institution; production product access and institution OAuth registration are separate from possession of developer keys.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Transactions sync returns added, modified and removed records with next_cursor and has_more, up to 500 updates per call. Initial history can cover up to 730 requested days, subject to institution availability; account-specific streams require their own cursors.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Plaid customer API | hybrid | Integration provider | Yes | App review | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The lowest eligible customer plan and any fixed API, partner or setup charges remain unestablished. Payment-processing charges do not by themselves establish an API-access surcharge.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
This assessment covers reading and synchronizing Transactions data, not moving funds. The sandbox transaction-creation endpoint is test-only; no production transaction mutation is established within the reviewed product.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
Persist updates and the final cursor only after a full pagination batch succeeds. A mutation-during-pagination error requires restarting from the batch’s original cursor; an eligible empty-cursor request can rebuild available Item updates, while webhook notifications only indicate when to poll. For TRANSACTIONS_SYNC_ITEM_LIMIT_EXCEEDED, keep the saved cursor: an empty-cursor restart is prohibited. Use /transactions/get or contact Plaid Support when the supported cursor path cannot continue.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Updates and deletion identities documented for the stated resourcesPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Sync returns additions, modifications and transaction removal identities for the selected Item/account stream. | Transactions API reference ↗/transactions/sync > added; modified; removedChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Saved cursors resume updates; an eligible empty-cursor request can rebuild available Item history. For TRANSACTIONS_SYNC_ITEM_LIMIT_EXCEEDED, keep the saved cursor: an empty-cursor restart is prohibited. Use /transactions/get or contact Plaid Support when the supported cursor path cannot continue. No retained replay guarantee is inferred. | Transactions API reference ↗/transactions/sync > cursor; count; Pagination instructionsChecked 2026-10-16 Transactions errors ↗TRANSACTIONS_SYNC_ITEM_LIMIT_EXCEEDEDChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Applications can retain structured, user-authorized transaction records and removal IDs outside Plaid. History depends on the connected institution, requested product and available period; this is not an export of the source bank’s full ledger, attachments or account configuration.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
Developers can build their own applications on Plaid’s APIs (and maintain their own transaction reconciliation). These technical docs do not establish ownership or portable export of a native Plaid workflow definition.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Structured API for the declared product scopePlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. The declared Transactions product exposes normalized financial-account transactions. | Transactions API reference ↗Transactions; /transactions/syncChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Iterate up to 500 updates per page; initial history is bounded by account/product availability. | Transactions API reference ↗/transactions/sync > count; cursor; next_cursor; has_moreChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Documented structured API filtersPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Date and account selection are documented; API records are not live bank SQL. | Transactions API reference ↗/transactions/get > start_date; end_date; optionsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | Separate provider consent or partner agreement requiredPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Full production product access requires application; some institutions also require OAuth registration. | Sandbox and limited production ↗Limited ProductionChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. The lowest eligible paid plan and route-specific fixed API charges have not been established. | Plaid Quickstart ↗Introduction > API Key; How it works; Making API requestsChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | Plaid Quickstart ↗Introduction > API Key; How it works; Making API requestsChecked 2026-10-16 |
| Which external write operations are documented? | -Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Assessed endpoints read or refresh bank data; sandbox creation does not establish production mutation rights. | Transactions API reference ↗Transactions > Endpoints; See alsoChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Approved third-party applications using fixed interfacesPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Custom apps use Plaid APIs, with separate production product and institution eligibility. | Plaid Quickstart ↗Get started with the Quickstart; IntroductionChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Documented updated-since filters or webhooksPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Poll scoped cursors after update webhooks; this is an API change feed, not source-bank database CDC. | Transactions API reference ↗/transactions/sync; SYNC_UPDATES_AVAILABLEChecked 2026-10-16 |
| How are integration limits disclosed? | Published numeric quotas and recovery instructionsPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Numeric per-Item and per-client limits and rate-limit error handling are published. | Rate Limit Exceeded errors ↗Transactions endpoints; Troubleshooting stepsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. The application receives structured records and removed transaction IDs. | Transactions API reference ↗/transactions/sync > added; modified; removedChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. A customer cancellation retrieval window and any exit charges have not been established. | Plaid Quickstart ↗Introduction > API Key; How it works; Making API requestsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Developers run their own integration code; native workflow artifact rights remain unresolved. | Plaid Quickstart ↗Quickstart setup; How it worksChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Plaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | Plaid Quickstart ↗Introduction > API Key; How it works; Making API requestsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Portable structured records on documented routes; whole-product completeness unverifiedPlaid Transactions read/sync for user-authorized Items and supported credit, depository and selected loan accounts; Transfer, Investments and Plaid Check are separate products. Portable transaction records are established within supported accounts and available history, not source-bank completeness. | Transactions API reference ↗Transactions; /transactions/getChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- The lowest eligible paid plan and route-specific fixed API charges have not been established.
- Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
- Assessed endpoints read or refresh bank data; sandbox creation does not establish production mutation rights.
- A customer cancellation retrieval window and any exit charges have not been established.
- Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.