Bank APIs and Aggregators Undermine Plaid
Plaid at $546M ARR growing 40% YoY
This pressure showed that bank connectivity was no longer a scarce input, it was turning into a low margin utility. Plaid made money each time a fintech user linked an account, refreshed balances, or pulled transactions. Once fintechs could route volume across Finicity, MX, or Stripe, or use bank APIs directly for key institutions, Plaid lost both pricing power and exclusivity, so lower customer growth translated almost mechanically into lower revenue growth.
-
Finicity and MX were not just backup vendors. Finicity became especially strong in lender workflows through Mastercard Open Finance and mortgage verification rails accepted by Fannie Mae and Freddie Mac. MX competed from the bank side as well, selling FDX and OAuth based data access infrastructure directly to financial institutions.
-
Stripe attacked from the adjacent stack. Financial Connections lets a merchant or platform use one Stripe integration to link accounts, verify ownership, check balances, pull transactions, and immediately turn that data into ACH debits, payouts, risk checks, or Treasury flows. That makes bank linking feel bundled, not standalone.
-
Banks launching direct APIs changed the economics even when Plaid stayed in the flow. Large banks pushed permissioned access through secure APIs and negotiated access agreements, which reduced the value of screen scraping infrastructure and shifted more leverage to banks controlling the underlying data. In that world, aggregators compete more on packaging and workflow than on raw access.
The market is moving toward account connectivity as a bundled feature inside bigger workflows, lending, payments, onboarding, and fraud. That favors platforms that can turn bank data into a decision or transaction in the same session. Plaid’s path is to keep moving up that stack, where Protect, Check, Identity, Signal, and Layer make each connection worth more than the connection itself.