Last week, OpenAI announced a new set of personal finance tools in preview for ChatGPT Pro users in the United States. Users can now connect their bank accounts, credit cards and investment portfolios directly to the tool, with Plaid managing account connections across more than 12,000 financial institutions.
At first glance, you’d be forgiven for seeing this as little more than a feature launch. In a sense, there isn’t necessarily anything new here. Customers have been using fintechs and third parties to aggregate and manage their finances for years, and engagement with incumbent providers remains relatively strong.
What is different this time is the ability for ChatGPT to move from giving pointers to a customer looking to build deposits to providing a list of potentially suitable accounts for them to consider. In other words, putting it in a central position to influence future product sales. The nightmare scenario of big tech playing this role in the value chain was mooted years ago, but never came to pass. This partnership will doubtless raise those same concerns again.
For senior executives at banks, the questions are urgent. What kind of threat will this pose to the customer relationship? What impact does it have on your ability to cross-sell? And how should banks be bringing open banking and AI together in their digital channels?
The consumer appetite for AI-driven financial management was already clear before this announcement. Our latest research, drawing on insight from 16,000 UK consumers per year through our Orion study, shows that 8% of adults are already using AI tools for financial advice or support. That figure may sound modest, but it skews towards the very segments many banks are striving to attract and retain: younger, more affluent and digitally engaged consumers.
More striking still is the gap between current behaviour and stated intent. Around 29% of UK banking customers say they are interested in AI-enabled financial solutions, which is roughly three times the proportion already using them. That equates to millions of people waiting for a credible provider to deliver it.
The Plaid and ChatGPT announcement shows OpenAI has decided it wants to be that provider. Banks need to decide whether they are going to compete, collaborate or cede the ground entirely.
Plaid provides the infrastructure for permissioned access to financial data, allowing customers to give consent for third-party applications to access their information. What the ChatGPT integration changes is not the underlying infrastructure, but the ambition of what sits on top of it.
To date, much of open banking has supported relatively narrow use cases: enhanced account aggregation, simpler product applications, or A2A payments. While these add value, none is transformative on its own.
What the ChatGPT integration does is place a sophisticated natural language interface on top of that data, one capable of contextualising spending patterns, surfacing savings opportunities, modelling financial scenarios, and responding to questions that consumers would never ask a branchadvisor.
According to OpenAI, more than 200 million people already use ChatGPT each month to ask finance-related questions. Until now, those interactions were limited by what the customer could provide. The Plaid connection changes that entirely, moving ChatGPT from something more akin to a reference tool towards something that can offer a form of personalised financial support.
The implication for banks is clear. If customers are directing financial questions to ChatGPT and it can answer based on their actual account data, the bank’s app becomes less important as a primary interface for financial insight.
The risk of framing this purely as a threat is that it misses the more important question: what could banks build if they combined their own data, their customer relationships, and AI capabilities in the same way, but with the trust advantage that only a regulated institution can offer?
Trust matters enormously here, and it is an asset banks still hold in relative abundance. When we ask consumers what would make them more comfortable with AI in banking, the answer consistently points to credible, regulated providers as their preferred source.
The architecture to build this already exists. The question is not whether the pipes are there; it is who builds the most compelling experience on top of them.
Three areas stand out where banks are well placed to compete.
1. Deep personalisation: Banks hold a wealth of contextual information on customers (e.g. lending history, product usage patterns, life stage signals), a significant data advantage that can be translated into genuinely useful experiences.
2. Proactive and agentic capability: Our research shows that more than one in five consumers is already comfortable with some level of automation in areas like savings, subscriptions and payments, and appetite is even stronger among those who lack financial confidence.
3. The ability to transact: Perhaps the biggest advantage for banks is the ability to allow customers to close the loop from advice to action.
The Plaid and ChatGPT announcement is the beginning of a more competitive phase in which the interface layer of financial services becomes genuinely contested territory.
This is not fundamentally a technology decision – it’s about product and positioning. The challenge is not whether to use AI or open banking, but how quickly banks can combine them in a way that is visibly useful to customers and credibly differentiated from what a generic AI platform can offer.
Our data clearly shows that consumer demand is running ahead of current bank propositions. Those using AI tools for financial advice are not waiting for banks to invent the concept, they are waiting for banks to deliver it. The window to do this on their own terms is narrowing.
If you’d like to understand where your customers sit on AI adoption – and what they expect next – get in touch for further insights from our surveys.
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| __hssc | 1 hour | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
| __hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
| AWSALBCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
| AWSALBTG | 7 days | Amazon Web Services set this cookie for load balancing. |
| AWSALBTGCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
| elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
| rc::a | never | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| rc::c | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| wpEmojiSettingsSupports | session | WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. |
| XSRF-TOKEN | 2 hours | This cookie enhances visitor browsing security by preventing cross-site request forgery. |
| Cookie | Duration | Description |
|---|---|---|
| AWSALB | 7 days | AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. |
| AWSALBTG | 7 days | Amazon Web Services set this cookie for load balancing. |
| AWSALBTGCORS | 7 days | Amazon Web Services set this cookie for load balancing. |
| Cookie | Duration | Description |
|---|---|---|
| __hstc | 6 months | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
| _ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
| _ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
| hubspotutk | 6 months | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
| wmc | 1 year 1 month 4 days | Workable sets this cookie to assign a unique visitor ID for statistical purposes. |
| Cookie | Duration | Description |
|---|---|---|
| _cfuvid | session | Description is currently not available. |