Open Banking regulation arrives in 2027 and most banks are treating it as a compliance problem. The ones that treat it as a design problem will own the next decade of financial services.
Most financial institutions track Open Banking as a regulatory and technology obligation. It is also the most significant forced redesign of the financial services customer experience since the ATM. The CEO who reads this as a compliance deadline will allocate it to the technology team and move on. The CEO who reads this as a design mandate will understand that when switching costs approach zero, the only durable competitive advantage is an experience the customer actively chooses. That is a design problem. It is also the only version of this problem worth solving.
The banking app was never designed around the customer’s financial life.
It was designed around the bank’s product portfolio. The navigation reflects the institution’s internal business lines: checking, savings, mortgage, credit card, investments. Each product lives in its own silo because a different team built it, a different channel acquired it, and a different P&L manages it. The customer’s financial life crosses all those categories at once, in ways the app has never been organized to reflect.
A person managing a household budget does not think in product lines. They think in goals: pay the mortgage, build the emergency fund, pay off the card before the rate resets, figure out why the check to the contractor has not cleared. The banking app makes them navigate five different sections to answer questions that belong to one conversation. And every year, the app gets more features and less coherent as new products get bolted onto an architecture that was never designed to hold them.
By 2027, that architecture will be legally required to open itself up. And most banks will spend the next twelve months trying to figure out how to comply with the minimum version of that requirement while protecting the lock-in that has kept customers from leaving despite an experience that would not survive comparison to any consumer product built in the last decade.
Those who understand what is actually happening will build something different.
What the CFPB Just Required
The Consumer Financial Protection Bureau’s Section 1033 rule, finalized in October 2024, requires financial institutions to provide consumers and their authorized third parties with standardized API access to their financial data. The largest banks face compliance deadlines beginning in 2026. The broader industry timeline runs through 2027 and 2028.
In plain language: a customer can now require their bank to share their financial data with any authorized service they choose. A budgeting app, a financial planning platform, a competing bank offering a better rate, an AI agent managing their financial life on their behalf. The data belongs to the customer. The bank is required to provide access to it.
This is the American version of what Europe implemented through PSD2 several years ago, and the European experience is instructive. Banks that treated Open Banking as a threat spent their energy building technical compliance while minimizing the utility of the APIs they exposed. Banks that treated it as a platform opportunity built financial data infrastructure that made them more useful to customers rather than less, because they understood that in an open data environment, relevance is earned, not inherited.
The US market is about to have the same reckoning. Every bank will build the required API. What they build behind it, the experience that determines whether a customer with full data portability stays or leaves, is the design decision that matters.
Why Switching Costs Are No Longer the Strategy
For most of the history of retail banking, the primary retention mechanism was friction. Changing your direct deposit is inconvenient. Updating your autopay connections takes a weekend. The thought of moving your mortgage and your checking and your credit card and your savings to a new institution, and re-linking all the services that connect to them, is enough to keep most people from acting on dissatisfaction that would have caused them to switch providers in any other category.
That friction was not designed. It was inherited from a fragmented data architecture and a regulatory environment that never required interoperability. It worked as a retention strategy not because the experience was good but because the cost of leaving was high enough to make staying the path of least resistance.
Section 1033 reduces that friction structurally. When a customer’s financial data is portable and third-party services can access it through standardized APIs, the technical barrier to switching drops to near zero. The switching cost that remains is the relationship cost: how useful is my current bank to my actual financial life, and would something else be more useful?
That question was always the right question for financial services to be competing on. It was just never the one the industry had to answer because the friction answered it for them.
By 2027, the friction answer is gone for a growing portion of the market. The design answer is what replaces it. And most banks have not built toward the design answer because they never had to.
The Two Strategies and Why Only One Compounds
There are two ways a bank can respond to a world where its customer’s data is portable and its switching costs are approaching zero.
The first strategy is protection.
The bank builds the minimum compliant API, invests in the parts of the customer relationship that remain structurally sticky, and competes on rate and product features rather than experience. It treats Open Banking as an external threat to manage rather than an internal transformation to lead. It watches the fintech ecosystem build the aggregation and intelligence layer on top of its own data, and it responds by trying to build competing versions of those products rather than becoming the platform they want to build on.
This strategy produces a bank that is slightly more compliant and significantly less relevant over a five to seven year horizon. The aggregation layer that sits above its data becomes the customer’s primary financial interface. The bank becomes infrastructure: reliable, necessary, invisible, and replaceable by any other infrastructure that offers equivalent rates and comparable FDIC protection.
The second strategy is redesign.
The bank starts from a different question: if our customer can take their data anywhere and the cost of leaving us approaches zero, what would we have to build to be the experience they would choose to stay for?
That question produces a fundamentally different product brief. It requires the bank to organize its experience around the customer’s financial life rather than its own product portfolio. It requires a data architecture that connects checking, savings, credit, and investment into a coherent view of a household’s financial position rather than a set of separate product relationships. It requires an intelligence layer that uses longitudinal transaction data to surface insights the customer could not easily produce themselves: when the household’s cash position is trending toward a shortfall, when a rate change on a variable product is about to affect the monthly payment meaningfully, when a goal the customer stated is on track or falling behind.
None of this requires technology that does not exist. It requires organizational decisions about what the product is for, decisions that most banks have never had to make because they competed on distribution and friction rather than value.
What the CUX Officer Has to Build That the Product Team Cannot
The Chief User Experience Officer in financial services in 2027 has a specific mandate that is different from the design work that preceded it.
The previous mandate was to make a complicated product less confusing. Better information architecture. Cleaner transaction flows. Improved mobile navigation. That work was valuable and most of it remains undone in most banking products. But it was optimization work: making the existing product better without changing what the product was fundamentally for.
The new mandate is to define what the product is for in a world where the customer can leave. That is a strategic question, not a design question. It becomes a design question only after someone at the organizational level has answered it, because the design of an experience that earns loyalty in a low-friction environment is completely different from the design of an experience that manages customers through high-friction architecture.
The specific problems the CUX officer has to solve in 2027 are three.
The first is the unified financial view. A customer whose data can now flow through standardized APIs should not have to use a third-party aggregation app to see their own financial position clearly. The bank that builds the best view of a customer’s complete financial life, including accounts the customer holds at other institutions, becomes the place the customer goes to understand their money even if they hold products elsewhere. That is not a threat to the bank’s products. It is the most powerful retention mechanism available in an open data environment: being the most useful place the customer has to think about their finances.
The second is the personalization layer that actually uses the data. Banks have been collecting transaction data for decades and using it primarily for fraud detection and regulatory reporting. The customer’s transaction history contains more accurate and actionable information about their financial behavior than any survey or stated preference. A bank that builds a personalization layer that uses longitudinal transaction data to surface relevant, timely, specific guidance, not marketing, genuine guidance about the customer’s actual financial situation, is building toward the trust that retains customers when switching costs disappear. That requires a data architecture decision and a product philosophy decision that have to happen above the design team.
The third is the agent-ready interface. By 2027, a meaningful portion of customers will be using AI agents to manage aspects of their financial lives. Those agents will need to interact with banking products on the customer’s behalf: checking balances, initiating transfers, understanding billing cycles, evaluating product options. The Section 1033 API is the authorization layer for this interaction. The experience design question is what the customer understands about what their agent did in their account, what authorizations are active, and how to audit or change them. That trust and transparency layer is not an engineering problem. It is a design problem that the CUX officer has to define before the engineers build the API scaffolding that makes it possible.
What I Would Do Starting This Quarter
If I am the CEO or CUX officer making this bet, I do not wait for the competitive market to demonstrate that experience is the new retention mechanism. By the time the market confirms it, the design lead time required to build a genuinely differentiated experience is already longer than the available window.
I commission a first-principles audit of the customer’s actual financial life: what goals they are managing, what questions they are regularly trying to answer, what moments in their financial year produce the most anxiety or confusion. Not a satisfaction survey. A behavioral analysis of what the transaction data shows customers actually doing and where they are failing or succeeding at the things they care about.
I build the unified financial view before I build any other new product. If the bank is going to earn the right to be the customer’s primary financial interface in an open data environment, it has to be the best place to see the customer’s complete financial picture. That is the foundation. Everything else is built on top of it.
I assign ownership of the agent-ready experience to a named person with cross-functional authority before the Section 1033 API build is scoped, because the authorization and transparency design for agent interactions has to be in the API specification from the beginning, not retrofitted after the technical build is done.
And I make the case internally that the experience work is not a cost center that reduces friction. It is the only retention strategy that works when friction is no longer available as a strategy. That case has to be made in the CEO’s language, which means it has to connect design decisions to customer lifetime value, to churn reduction, to the specific competitive dynamic that Open Banking creates in the customer segments that matter most.
The banks that build toward that case in 2026 and 2027 will be the ones that look inevitable in 2029. The ones that build the minimum compliant API will be funding the aggregation platforms that replaced them.
Sources: Consumer Financial Protection Bureau, “Personal Financial Data Rights Final Rule (Section 1033),” October 2024; Deloitte Center for Financial Services, “Open Banking and the Future of Financial Services,” 2025; McKinsey Global Institute, “The Future of Retail Banking,” 2026; Forrester Research, “Banking Customer Experience Index,” 2026; J.D. Power, “U.S. Retail Banking Satisfaction Study,” 2026; Bank for International Settlements, “Open Banking: How Far Has It Come and Where Is It Going,” 2025.