Build native integrations through our scalable Unified APIs
Showcase integrations, partners, and apps to your customers
Apideck and Plaid have signed a partnership. Coming soon.
One integration. Every bank feed network.
Integrate the Bank Feeds API once. Apideck posts statements natively into Xero, NetSuite and the rest today, feeds QuickBooks Online through Intuit Bank Feeds (early access), and lists you on Plaid next.
Your Application
Your customers’ accounts
- Harbor Bakery
- Atlas Freight
- Lumen Studio
Select a transaction to inspect its payload
Lumen Studio’s cash-flow app
On the Plaid network
Balance at Your Application
$9,623.10
Atlas Freight’s QuickBooks Online
Through Intuit Bank Feeds
Latest for review
Freight invoice paid
Harbor Bakery’s Xero
Native bank feed
- Flour supplier−470.55Match Bill FLR-311
- Card sales, daily settlement+1,832.40Match INV-1043
- Routed this session
- 0
- To Plaid apps
- 0
- To QuickBooks via Intuit
- 0
- To native feeds
- 0
Simulated data and sample customers. Each customer’s transactions go to the system that customer uses; Plaid and Intuit request them on their own schedule, native feeds receive statements as you post them. One integration on your side serves all of them.
Integrate once. Apideck reaches every network.
Your business customers live in different tools. You build one Bank Feeds integration and Apideck takes your accounts to each of them, by the route each one accepts.
Your Application
One Bank Feeds API
The Plaid network
Coming soonBusiness finance apps such as lending, spend and cash-flow tools, plus Xero in the US, Zoho Books, FreshBooks, Wave, Acumatica, Odoo and Campfire.
Intuit Bank Feeds
Early accessQuickBooks Online, through Intuit’s own bank feed program, on the same FDX provider as Plaid.
Native statement feeds
LiveStatements posted straight into Xero, NetSuite, Sage Intacct, Exact Online, Moneybird, Pennylane, Snelstart, Twinfield and more.
What you would build without it
- Plaid
- Run an OAuth server, the FDX endpoints, consent handling and Plaid’s validation
- QuickBooks Online
- Join Intuit’s data-provider program and operate an FDX provider for it
- Every other ledger
- A separate integration, partnership and certification per accounting platform
- Sign-in
- A different customer sign-in for each network
What is Plaid Bank Feeds?
Plaid Bank Feeds is the common name for listing a financial platform on the Plaid network, so its accounts can be linked from the apps and accounting software that use Plaid. The product underneath is Plaid Core Exchange, an API specification built on the FDX standard. The platform exposes accounts, balances and transactions, and Plaid retrieves them for each app a customer connects. Doing it yourself means running an OAuth server, the FDX endpoints and Plaid’s validation. With Apideck it is one more route behind the Bank Feeds API you already use to push statements into accounting platforms, served by FDX Connect, the same provider that already feeds QuickBooks Online through Intuit Bank Feeds.
Found by name, across the whole network
A native bank feed connects one customer to one accounting platform. A Plaid listing makes Your Application a searchable institution in every app and accounting platform that uses Plaid.
- Apps on the Plaid network, which Plaid puts in the thousands, including business finance tools
- Xero in the US, Zoho Books, FreshBooks outside the US, Wave, Acumatica, Odoo and Campfire
- Listed as Your Application, with your logo, not as Apideck
App categories are illustrative. Accounting platforms shown are those whose own help docs name Plaid as a bank connection provider.
Your Application
Listed on Plaid
Xero USLending
Zoho BooksSpend management
FreshBooksCash-flow forecasting
WaveAP automation
Acumatica
CampfireTreasury tools
OdooThousands more appsEmbedded or direct, the same architecture
Whether you power accounts inside other platforms or serve your own customers, the planes do not change. Only who owns the sign-in does.
Your Application powers accounts inside partner platforms, such as marketplaces or vertical software. Each partner owns the login and the brand, so its customers find the partner’s name in the bank list. Your Application sends data once; nothing changes for it per partner.
Apideck is never in the money path. A bank feed carries data; money stays with Your Application.
What is FDX Connect?
The provider in the middle of every diagram on this page.
FDX Connect is Apideck’s data provider built on FDX, the open banking standard that Intuit and Plaid both read. You never call it: you post accounts and statements to the Bank Feeds API, and FDX Connect serves them to the networks that pull.
- An OAuth and OpenID Connect sign-in server, with one issuer per listing, so each brand you power is its own institution
- A signed handoff to your existing login and MFA; it never sees a password and never knows who the customer is until your login says so
- The FDX read endpoints networks call: accounts, balances and transactions, scoped to the accounts each customer chose
- Live today for QuickBooks Online through Intuit Bank Feeds (early access); Plaid Core Exchange next, built and in validation with Plaid
Signed in on your login, with your MFA
Core Exchange puts the customer on the institution’s own login. With Apideck that is the Your Application login they already trust. Step through it.
A customer of Your Application links their business account inside a finance app that uses Plaid, say a cash-flow or lending tool. The sign-in is Your Application's own, Plaid shows the account picker, and Apideck serves the data through Core Exchange.
Link an account
Connect instantly
Log in to your bank
Enter details manually
Takes 1 to 3 business days
Step 1 of 8
Plaid’s standard flowThe customer links a bank in an app
Plaid
ApideckThe app opens Plaid Link with a link token from its own server. Nothing has reached Your Application or Apideck yet.
Illustrative walkthrough with sample data. Screens are simplified mock-ups, not Plaid’s, Xero’s or any app’s actual interface.
Native feeds today, Plaid next
A native feed reaches a ledger with full statement control. A Plaid listing reaches a network. Apideck picks the route per connection, so you get both from one API.
- Native bank feeds
- 10
- Live today
- Intuit Bank Feeds
- 1
- Early access
- The Plaid network
- 7
- Coming soon
- Journal-entry fallback
- 23
- Live today
34 accounting platforms are reachable today through one Accounting API integration; the Plaid route adds FreshBooks and Wave. Counted as platforms: Exact Online’s regional editions and both Sage Intacct APIs count once each.
Connector details in the docsNative bank feeds
Live today, 10 platformsStatements pushed straight into the ledger’s own bank feed
Intuit Bank Feeds
Early access, 1 platformIntuit pulls from the same FDX provider that serves Plaid
The Plaid network
Coming soon, 7 platformsAccounting platforms whose own docs name Plaid for bank connections
Journal-entry fallback
Live today, 23 platformsTransactions posted as journal entries through the Accounting API. No reconciliation queue, and a different call from bank-feed-statements.
AFAS
Alegra
Business Central
DualEntry
e-Boekhouden
Fortnox
FreeAgent
Holded
Intuit Enterprise Suite
MRI Software
MYOB Acumatica
MYOB Business
Procountor
Restaurant365
SAP S/4HANA Cloud
Spiris
Visma eAccounting
Wafeq
Workday
YukiFrom signed partnership to your own listing
Most of the stack already runs today for Intuit Bank Feeds, in early access. Going live on Plaid is an onboarding, not a build.
- 1
We set up your institution
Your brand name, logo and login address. Platforms that power several brands get one listing per brand.
Apideck
- 2
You add one step to your login
Verify Apideck’s signed request, sign the person in with your own MFA, return a signed result.
You
- 3
You send account data once
Accounts and statements through the Bank Feeds API, the same call that feeds the native accounting routes.
You
- 4
Your listing goes live
We take it through Plaid’s validation and publish it as its own institution, under your name.
Apideck and Plaid
- 5
Customers search, sign in and share
In any Plaid-powered app they find your name, sign in on your login and choose accounts.
Customer
- 6
We serve the right accounts only
Each request returns only what that person holds with you, even if they use other platforms we serve.
Apideck
Three calls, every route
Connect a customer’s ledger once, register each account once, then post statements as transactions settle. The statement call is the same for Plaid, Intuit and every native bank feed.
On the Plaid and Intuit routes the customer starts in an app, so there is no Vault step. You add one endpoint to your login for the signed handoff instead.
Every statement:
- Reconciles to the cent: start balance + credits − debits = end balance
- Unsigned amounts: the direction lives in credit_or_debit
- A stable source_transaction_id: one per line, the key ledgers use to reject duplicates
Authorization: Bearer <APIDECK_API_KEY>x-apideck-app-id: <APP_ID>x-apideck-consumer-id: <CUSTOMER_ID>{ "bank_feed_account_id": "bfa_01H8X9Y2A3B4C5D6E7F8G9H0J1", "start_date": "2026-10-01T00:00:00Z", "end_date": "2026-10-07T23:59:59Z", "start_balance": 45812.40, "start_balance_credit_or_debit": "credit", "end_balance": 48212.40, "end_balance_credit_or_debit": "credit", "transactions": [ { "source_transaction_id": "txn_01H9A2B3C4D5E6F7G8H9J0K1L2", "posted_date": "2026-10-07T09:12:00Z", "description": "Payout to seller account", "amount": 2400.00, "credit_or_debit": "credit" } ]}
Built for platforms that hold the money
- Corporate card issuers
- Cardholders link the card program in the spend and accounting tools they already use.
- Embedded banking and treasury
- Accounts you hold for merchants become findable by name, like any other institution.
- BaaS and multi-brand platforms
- One listing per brand you power, each under its own name and login, from one integration.
- Payouts and marketplaces
- Sellers see balances and payouts next to their bank accounts, where they reconcile.
What Plaid receives
- Accounts, with name, type, currency and status
- Current and available balances
- Posted transactions
- Account holder name, email and address
- Account and routing numbers
What it does not
- Money. A feed carries data. What an app does with a linked account is its own product.
- Passwords. Customers sign in on your login. Plaid and the app never see credentials.
- QuickBooks. Intuit does not take institution data through Plaid, so it has its own route.
Before you go live
Tick what you already have. None of it is new infrastructure, and most platforms that hold accounts are close. Finish the list and book a call to plan your listing.
A Plaid connection you can verify
Not every Plaid listing runs on the same specification. Here is what sits behind ours.
Core Exchange from day one
Plaid’s current FDX-aligned specification. Never the legacy Plaid Exchange, which is closed to new integrations.
Checked against Plaid’s published spec
Every response is validated against Plaid’s public specification in our build. A response that does not conform cannot ship.
One provider, two networks
The FDX data provider that serves Intuit Bank Feeds for QuickBooks Online also serves Plaid. One sign-in contract for both.
One API for every route
Plaid sits behind the Bank Feeds API next to the native routes. Add a route without touching your integration.
Europe included
The accounting platforms on Plaid are mostly in the US and Canada. Statements also go straight into Exact Online, Moneybird, Pennylane, Snelstart and Twinfield.
A member of FDX
Apideck is a member of the Financial Data Exchange, the standards body behind the specification Core Exchange builds on.
Questions to ask any Plaid provider, including us
Several vendors offer a Plaid listing. These separate a listing built for the network Plaid runs today from one built for the network it is retiring.
- Does your listing run on Core Exchange?
- Plaid has closed Plaid Exchange to new integrations. A listing built on it starts life on a migration path.
- Where does my customer sign in?
- Core Exchange expects your own login on your own domain, with a second factor. A phone number and SMS code on someone else’s screen is the old model.
- Does the same person on two platforms see only the right accounts?
- One person can hold accounts at several brands you power. Each listing has to keep their identity separate.
- How does my second brand get listed?
- An API call and an onboarding, or a ticket in a support queue? It decides how fast you can grow.
- Which ledgers take statements directly?
- Plaid reaches a handful of accounting platforms, mostly in North America. QuickBooks and the European locals need native routes.
- Can I see the conformance results?
- Ask for evidence against Plaid’s published specification, not a description of it.
Put your application on the Plaid network
Early access is open to platforms that already hold account and transaction data. We onboard the first listings ourselves and take each one through Plaid’s validation with you.
Listed under your own name
Your brand and logo in every bank list, and customers sign in on your own login.
Start with native bank feeds now
Plaid joins behind the same call later, with no rework.
Shape what comes next
Which networks follow Plaid, and which ledgers and markets we add.
Questions
What is Plaid Bank Feeds?
Plaid Bank Feeds is the common name for listing a financial platform on the Plaid network so its accounts can be linked from apps and accounting software that use Plaid. The Plaid product underneath is Plaid Core Exchange, an API specification built on the FDX standard: the platform exposes accounts, balances and transactions, and Plaid retrieves them on behalf of the apps an account holder connects. Apideck’s upcoming Plaid connector serves Core Exchange for you, behind the same Bank Feeds API that already pushes statements into accounting platforms such as Xero, NetSuite and Exact Online.
Is Plaid Core Exchange the same as Plaid Exchange?
No. Plaid Exchange is Plaid’s older provider integration, built on a proprietary schema and closed to new integrations; Plaid is migrating its providers to Core Exchange. Core Exchange is the current specification and is aligned with FDX. Apideck’s connector is built on Core Exchange only. When you compare providers, ask which specification a listing runs on.
Which accounting platforms can read a feed through Plaid?
Accounting platforms whose own documentation names Plaid as a bank connection provider include Xero in the United States, Zoho Books in the US and Canada, FreshBooks in Canada, the UK and Europe, Wave in the US and Canada, Acumatica, Odoo in the US and Canada, and Campfire in the US. Outside those platforms and regions, the Bank Feeds API keeps using each ledger’s native route.
Does QuickBooks Online use Plaid for bank feeds?
No. Intuit runs its own aggregation and accepts institution data directly from data providers under its own program, not through Plaid. Apideck reaches QuickBooks Online through Intuit Bank Feeds, currently in early access, which runs on the same FDX data provider as the Plaid connector. Your integration is the same Bank Feeds API either way.
Should I use Plaid or native bank feeds?
Both, and you do not have to choose in code. Native bank feed routes stay primary wherever an accounting platform has one, because they push full statements with opening and closing balances the ledger can validate. Plaid adds reach where there is no native route, and it adds every Plaid-powered app beyond accounting, such as lending, spend management and cash-flow tools. Apideck routes each connection through the right path behind one Bank Feeds API.
Does a Plaid listing move money?
No. A bank feed carries data: accounts, balances, transactions and account details. Plaid does not move money through Core Exchange. If an app on the Plaid network offers transfers from a linked account, that is the app’s own product, running on its own payment rails.
Who sees my accounts on the Plaid network?
A Core Exchange listing makes your platform discoverable by name across the Plaid network. Nothing is shared until an account holder chooses to connect: they sign in on your platform, pick the accounts, and can revoke access per app at any time. Plan your account holder communication accordingly, for example a help article that lists the popular apps your customers use.
What is FDX Connect?
FDX Connect is Apideck’s data provider built on FDX (Financial Data Exchange), the open banking standard that Intuit and Plaid both read. Platforms never call it directly: they post accounts and statements to the Bank Feeds API, and FDX Connect serves them to the networks that pull. It runs an OAuth and OpenID Connect sign-in server with one issuer per listing, hands sign-in off to the platform’s own login and MFA with a signed request, and exposes the FDX read endpoints for accounts, balances and transactions, scoped to the accounts each customer chose. It serves QuickBooks Online through Intuit Bank Feeds today, in early access, and Plaid Core Exchange next.
Do I need to implement Plaid’s Core Exchange specification myself?
No. Implementing Core Exchange means running an OAuth authorization server, the FDX read endpoints, consent handling and Plaid’s validation process. Apideck runs that provider for you. You push account and transaction data through the Bank Feeds API, and the account holder sign-in happens on your own domain through a handoff Apideck provides.
When is the Plaid connector available?
Apideck and Plaid have signed a partnership, and the connector is upcoming. Early access is open to platforms that already hold account and transaction data, such as card issuers, embedded banking and payout platforms. Request early access on this page and we will walk you through onboarding and Plaid’s validation.