Akoya Could Disintermediate Plaid

The real risk is that Plaid can lose control of its most valuable bank connections even while demand for bank data keeps growing. When a giant bank or core data provider says access must run through Akoya, Plaid stops being the gatekeeper and becomes just another reseller or front end. That matters most in the enterprise tier, where a few large institutions can shape pricing, permissions, and product design for everyone downstream.1 2 3 4 5

• Plaid originally won with easier docs, self serve onboarding, and a clean API, not with unique bank pipes everywhere. Internal research on the aggregation market shows most providers share overlapping coverage, while banks are steadily pushing everyone toward the same API rails. That makes control of institution relationships more important than pure developer love.2 3
• Akoya is built for that control point. It presents itself as a one to many network for permissioned consumer data, follows FDX based APIs, and handles data sharing relationships on behalf of banks and recipients. That is structurally attractive to large institutions that want standardized contracts, fewer bilateral integrations, and no credential sharing.4 5 6
• The 2025 JPMorgan resets showed both paths in parallel. JPMorgan renewed with Plaid on September 16, 2025 and the agreement included pricing, while JPMorgan and Akoya also renewed on November 18, 2025. That means top banks are not choosing developer friendliness over bank control, they are making intermediaries pay and fitting them into bank governed rails.1 4 7 8

This pushes Plaid to become more valuable above the raw connection layer. The next phase is winning with fraud, identity, credit, payments, permissions, and bank tooling so that even if banks own the pipe, Plaid still owns the workflow fintechs pay for. The more open banking access looks like regulated utility infrastructure, the more Plaid has to monetize software on top of it.2 7