The Connector Podcast - FinanceX #23 - Beyond Banking & Sustainability - The Invisible Bank

You know, if you break your arm, right, the medical diagnosis is usually just this moment of absolute total clarity.

Oh, yeah. For sure.

Like, you go to the hospital, they take an X-ray, and right there on the screen is this jagged white line. It's a totally binary reality. The bone is broken, or, you know, it is not broken. You put a cast on it, you let it heal, and you just move on. And I bring this up because for the longest time, The world of banking operated with that exact same clean, binary simplicity.

Oh, absolutely. The lines were so clearly drawn.

Yeah. You had a bank, you walked into the physical branch of that bank, the bank held your money, they owned all the technology, and they shouldered all the regulatory burden. It was all just neatly contained in one, you know, marble building.

Right. And that boundary provided a tremendous sense of control for them. I mean, the institution knew exactly where its jurisdiction started and where it ended. But if we stretch that medical analogy just a bit further—

Please do.

Modern finance has basically moved out of the orthopedics ward and into the realm of neurology or maybe immunology. The X-ray machine is just entirely useless now.

Wow. Okay.

Yeah. We are no longer looking at a single isolated broken bone. We're looking at a deeply interconnected continuous orchestration of variables. It's this global nervous system where the boundaries between, say, a tech company, a retailer, and a financial institution have just completely dissolved.

That's a wild way to think about it, but it's so true. Which really brings us to our mission today. So welcome to the deep dive. If you are joining us, you might be a financial professional, maybe a compliance officer, an engineer, or simply a curious learner who just realized that the ridesharing app on your phone is suddenly offering you an insurance policy and a line of credit.

Yeah, which is happening all the time now.

Constantly. So today we are opening up an incredibly dense, just fascinating stack of material from the 23rd edition of FinanceX Magazine. And this entire issue is dedicated to providing you with actionable lessons for navigating the twin titans of modern finance.

Right, which are beyond banking. So essentially the maturation of embedded finance and sustainability.

Exactly. And the overarching thesis of this 23rd edition, which we're going to get into, is that the new reality of financial services is all about orchestration. It is not about ownership anymore.

No, not at all. The days of hoarding every single aspect of the customer journey, they're just over. The goal for anyone navigating these massive regulatory and infrastructure changes is figuring out how to successfully participate in this invisible layer, this layer that's just being woven into the wider economy.

Invisible layer. I love that phrasing. If you want to know how to survive and actually thrive in the next decade of finance, this deep dive is your blueprint. We are unpacking the exact mechanisms behind these changes. But, you know, before any institution can go beyond banking and participate in this new ecosystem, they have to face a pretty brutal reality about their own internal wiring.

Oh yeah. The internal plumbing.

Right. Because before you can step outside the bank, you have to fix what is inside the bank.

And that internal friction is arguably the single largest existential threat to legacy institutions today. I mean, for most of the past decade, executives and technology leaders have been totally paralyzed by what the industry framed as a binary choice. It was this great infrastructure illusion.

Okay, let's unpack this illusion because I know this is a huge pain point.

It really is. So on one side of the spectrum, you had the massive, highly disruptive rip-and-replace strategy.

The idea that you literally have to tear the house down to the studs.

Completely. The pitch from consultants was that a bank had to rip out its legacy core, these massive mainframe systems that had been running the institution for like 40 years, and replace them entirely with a modern cloud-native architecture.

Which sounds terrifying.

The implications are completely terrifying. We're talking about staggering capital expenditure, Incredible operational risk and digital transformations that stretch out over, you know, 5 to 10 years.

Yeah, I mean, we've all read the postmortems of those projects in the financial press. A bank announces a billion-dollar IT overhaul, the timelines slip by half a decade, the budget triples, and by the time the new system is finally turned on—

The market's already moved on.

Exactly. The market has already moved on to a completely different technological standard. It really feels like trying to change the engines on a 747 while it's flying over the Atlantic Ocean in a thunderstorm.

That's the perfect way to describe it. And because of those horror stories, many institutions just retreated to the other side of that binary choice, which is the do-nothing approach.

Or I guess more accurately, the do-the-bare-minimum approach.

Right. The bank basically accepts that its legacy estate is untouchable. So they just try to build these clumsy workarounds on the periphery. They let those old mainframe systems constrain what they can actually offer to their customers and how they interact with counterparties.

But the Finance X material makes a really compelling case that doing nothing is no longer just a slow decline. It's actually a rapid path to total irrelevance.

Yeah, the clock is ticking fast.

And to understand why, we really have to look at the mechanics of how those old systems actually operate versus what the modern world demands today, because those legacy mainframes I mean, they're actually brilliant at what they were originally built to do, right? Which is batch processing.

Yes. Let's unpack that mechanism because it's so central to the problem. Batch processing means the system aggregates a massive pile of transactions throughout the entire day. And then usually around, say, 2 in the morning, the system essentially locks the digital doors, goes completely offline, and processes all those transactions sequentially to update the central ledger.

Right. Which is a highly efficient way to manage computing power if you are living in the 1980s.

Exactly. If it's 1985, that is cutting-edge efficiency.

But the modern global economy does not go to sleep at 2 AM.

No, it really doesn't.

We are living in a world that demands continuous real-time operation. I'm talking about real-time payment rails where money moves in milliseconds, continuous cross-border settlement, intraday liquidity management where, you know, corporate treasurers need to know their exact capital position at 2:14 PM on a Tuesday.

Near-instant regulatory reporting. You can't forget that part.

Yes. So how do you do that on an old system?

Well, you can't. You simply cannot execute real-time continuous settlement on a piece of architecture that requires a 4-hour maintenance window every single night just to balance its own books. The pacing of the external world has simply outgrown the mechanical cadence of the legacy core.

Okay, so if ripping the mainframe out is a recipe for a billion-dollar disaster, And leaving it alone means your bank suffocates because it can't operate in real time. What is the third way?

This is where the Finance X sources introduce a paradigm shift that completely reframes the problem. They argue that modernization should not be viewed as replacement. It should be viewed as arbitrage.

Arbitrage. That's a fascinating word choice.

It's a brilliant conceptual framework for this. So in traditional finance, right, arbitrage is the practice of taking advantage of a price difference between 2 or more markets. You buy low in one place and sell high in another simultaneously.

Right. You're exploiting the gap.

Exactly. So, in the context of technology modernization, arbitrage means taking advantage of the specific strengths of different architectural eras rather than forcing one era to do everything.

Okay. Let me try to ground this with an analogy for you, the listener, because when you are staring down a multi-year IT roadmap, The concept of architectural arbitrage can feel a bit abstract.

Yeah, it gets a bit theoretical.

So, think about the modern smartphone sitting in your pocket right now. When you go to the store to buy a new phone, you are not buying a single monolithic application that handles every single function.

Right.

Like, you're not buying a device where the calculator, the camera, the map, and the phone dialer were all written into one massive block of inseparable code.

No, you are buying an operating system. You are buying iOS or Android.

Exactly. You are buying an orchestrator. The operating system sits right in the middle. It securely manages the core hardware, so the battery, the memory, the physical camera lens, but it provides this standardized layer that allows thousands of different third-party applications to sit on top and function smoothly.

You basically compose your own experience.

Yeah. The operating system handles the friction between the deep hardware and the agile software. And the Finance X text argues that enterprise banking infrastructure must move in this exact same direction.

This is highlighted beautifully in the insights from Brad Goad. He's a global head of banking and payments at DXC Technology. He outlines a strategy of treating the new bank architecture as literally a financial services operating system.

Okay, how does that work in practice?

He points specifically to platforms like DXC's Core Ignite. So the strategy is to leave the legacy mainframe in place to do the one thing it does better than anything else on Earth, which is maintaining the Because those mainframes are, like, virtually bulletproof when it comes to keeping track of the final tally of who owns what, right? Mm-hmm.

They process a massive share of global daily deposits flawlessly.

They do. They are incredible at that. So you retain that bedrock, but you insert this new operating system layer, this orchestration layer, directly above it.

Oh, I see.

This layer acts as a structural buffer. It integrates the agile, cloud-native fintech applications on the front end, and it translates those real-time demands into instructions the legacy mainframe can actually handle on the backend.

Which means you drastically compress your deployment timelines.

Exactly. You do not have to wait 7 years to rewrite the core ledger just to launch a new digital lending product. You can launch the product on the orchestration layer in a matter of months.

Okay, but wait, let me push back here on behalf of the engineers and the CFOs listening.

Mm-hmm.

Because a very common counterargument you hear is, look, I have 50 million lines of COBOL code that was written before most of my engineering team was even born.

Oh yeah, the COBOL problem.

Instead of buying an orchestration layer, why don't I just use some automated AI tool, translate all that COBOL into Java, stick it on a cloud server, and just call the problem solved? I mean, isn't treating this as a simple language translation the easiest fix?

That is perhaps the most dangerous trap in modern banking. And the source material is explicitly warning against it.

Really?

Why? Because treating infrastructure modernization purely as a code conversion exercise is practically guaranteed to end in disaster. To understand why, we have to look at what that legacy code actually represents. Those mainframes are not filled with clean, logical, perfectly documented lines of code. They are archaeological digs.

An archaeological dig? That paints a very specific picture.

Imagine digging through the strata of an ancient city. You find a Roman wall, right? And built directly on top of it is a medieval bakery. And then running right through the middle of that is a Victorian sewer pipe.

That sounds chaotic.

That is exactly what a 40-year-old banking core looks like. It is a massive accumulation of undocumented, highly tactical fixes.

Okay, give me a concrete example of how that happens mechanically. Like, how does a bank become an archaeological dig?

Okay, let's say in 1985. A specific country introduced a temporary withholding tax. An engineer wrote a patch in COBOL to accommodate that tax. 7 years later, in 1992, the bank launched a new cross-border corporate product, and another engineer wrote a patch that deliberately bypassed the 1985 tax code just for that specific product.

Right. A quick fix.

Exactly. Then in 2004, a 3rd engineer added a compliance routine that relies on the timing of that 1992 patch.

Oh, man. And let me guess, none of this is documented in a central manual. The only person who understood the dependency chain is an engineer named, like, Gary, who retired to a golf community in Florida a decade ago.

Precisely. Gary is playing golf and the bank is flying blind. The functionality encoded in those mainframes has accreted over decades of regulatory panic, mergers and acquisitions, new product launches—

So if you just translate that—

If you take that deeply tangled, completely undocumented mess, and simply run it through an automated translator, you have not solved your business problem. You have just moved the mess from one language to another. You took COBOL spaghetti and turned it into Java spaghetti.

And the Java spaghetti is probably running on a much more expensive cloud server. So you've achieved basically nothing except increasing your monthly computing bill.

Right. The FinanceX material emphasizes that before any of that architecture can be rewritten or translated, it has to be understood, rationalized, and then deliberately redesigned around the business outcomes the bank wants to achieve today.

So, you have to ask, how do we want to originate a loan in 2026? Not, how do we translate the code that originated a loan in 1995?

Exactly. If you skip that rationalization step, you spend millions of dollars just to build a slightly newer version of yesterday's bank.

Wow. Okay, this is a massive actionable lesson for you listening right now. Do not confuse translation with transformation. Modernization has to happen at the architectural layer. Keep the bedrock of the ledger, but build that highly flexible API-driven orchestration layer on top of it.

Yes, because once that internal friction is removed, and only when it is removed, can the bank finally do what every board of directors is demanding, which is to step outside its own walls and embed itself into the wider digital economy.

Which transitions us perfectly into the realities of Embedded Finance 2.0. Because once you have an operating layer that can communicate in real time with the outside world, you enter this battle for customer context.

And to be abundantly clear, embedded finance has moved way, way past the era of just slapping a payment button on a checkout page.

Right. The evolution of the narrative here is fascinating. If you rewind just, I don't know, 5 or 6 years, the dominant storyline in the financial press was the fintech disruption myth.

Oh, that was everywhere.

The idea was that these sleek, heavily funded, non-bank technology companies were going to swoop in, steal the entire customer relationship, Absorb all the lucrative payments and lending margins, and legacy banks would just be completely crushed.

Or in the best case scenario for the banks, they would be reduced to invisible dumb pipes, just a utility providing wholesale capital while the tech companies got all the glory.

Yeah, the dumb utility fear was palpable in every boardroom, but the reality that has actually played out, as detailed in the Finance X report, is fundamentally different. Embedded finance is not about tech companies replacing banks. It is about a massive shift in who owns the moment of demand.

The moment of demand. Let's dig into that because it's crucial.

Yeah, please.

Historically, a bank owned the entire context of a financial transaction. If you wanted to buy a car and needed financing, you mentally separated the shopping from the financing.

Right. You went to the lot, looked at a car, and then—

And then you purposefully drove to a physical bank branch, sat across a mahogany desk from a loan officer, and formally requested money. The bank was the destination.

They owned the real estate, the conversation, and the context.

But today, the moment of demand belongs to the platform. You are sitting on your couch, looking at a car on an automotive app, and the financing option is just a small slider you adjust within that exact same app.

You never leave the digital environment of the car marketplace.

No, you don't. The app owns the context, The bank is simply the invisible engine providing the capital in the background.

Dr. Manuel Tomit from Simpulse—he's their head of embedded finance and boss—he puts this beautifully in the text. He says financial services are moving from a destination you visit to an invisible layer beneath everyday experiences.

Yes, but here is the crucial part that really dispels that dumb pipe myth. Yeah, those tech platforms do not actually want to become banks.

Wait, really? They don't want to cut the bank out entirely? Not at all.

Providing a sleek user interface is one thing; actually operating. Creating a bank is a fundamentally different, deeply burdensome reality. Tech companies want the user engagement, but they absolutely do not want the burden of holding massive capital reserves.

Oh, right, the regulation.

Exactly. They do not want to build anti-money laundering compliance engines, and they certainly do not want to deal with teams of federal bank examiners auditing their books every single quarter.

So they want the fun part of finance, not the heavy lifting. The banks still provide the critical, highly regulated infrastructure. They have the balance sheet, the deep capital reserves, and the institutional trust that underpin the entire global system.

Embedded finance is just a division of labor.

It is a division of labor, and we have watched this division mature in distinct stages. Stage 1 was basic payments. Think of Apple Pay. It made the checkout process frictionless. You didn't need to pull out a physical piece of plastic issued by your bank; your phone just handled the handshake.

Right. And Stage 2?

Stage 2 was point-of-sale credit, popularized by companies like Klarna, Which normalized buy now, pay later for smaller consumer goods.

But the sources are telling us that we are now entering stage 3. Embedded finance is moving away from just facilitating the purchase of a pair of sneakers, and it is moving into heavy-hitting core relationship products. Yes, we are talking about long-term savings accounts, massive corporate lending, and complex insurance policies being embedded directly into non-financial platforms.

The global examples in the text really illustrate this maturation. Like, look at Southeast Asia and a platform like Grab. Grab originally launched as a simple ride-hailing app, just a utility for getting from point A to point B.

But over time, they recognized they had massive, high-frequency engagement with their users. Today, Grab is a super app. The payments, the lending to their drivers, and the insurance for the rides are increasingly integrated into single unified customer journey.

And we see the exact same thing in Latin America with Mercado Pago, which is the fintech arm of the massive e-commerce platform Mercado Libre. They started by just processing the payments for the marketplace, and now they're offering this massive suite of credit and insurance products directly to the merchants and consumers on their platform.

But perhaps the most illustrative example for legacy institutions is a partnership highlighted in the UK between NatWest, which is one of the largest traditional banks in the country, and Sainsbury's, the massive supermarket chain.

I love this example because it is just so grounded. Let's roleplay this for a second to really understand the mechanics.

Okay.

Imagine you are walking down the produce aisle at Sainsbury's, putting organic tomatoes in your cart. You open the Sainsbury's app to scan a barcode or check your loyalty points. In this new paradigm, what is actually happening between the supermarket In that moment, Sainsbury's, the brand, is providing the customer relationship.

They provide the everyday context, the loyalty engine, and the behavioral data. They know what you buy, when you shop, and how much you spend. They have your attention multiple times a week.

Right. And NatWest?

NatWest, the bank, is completely invisible in that produce aisle. But NatWest provides the balance sheet, the underwriting algorithms, the capital, and the massive regulatory muscle required to legally originate a financial product.

So when the Sainsbury's app suddenly offers me a targeted credit card or a personal loan or an insurance product on my groceries, the supermarket is just the storefront.

Yes.

The bank is doing the actual financial heavy lifting.

Exactly. It is a symbiotic organism. Sainsbury's gets to monetize its customer base much more deeply without having to actually become a regulated bank. And NatWest, NatWest gets to acquire customers and issue highly profitable loans without having to spend millions of pounds on billboard advertising trying to convince people to actively visit natwest.com.

It drastically lowers the cost of customer acquisition for the bank. And the commercial reality of this model is no longer speculative. For a long time, there was deep skepticism inside traditional institutions. Executives would ask, is this just a lab experiment for our digital innovation team? Are we actually going to make real money being an invisible provider?

Well, the survey data in the FinanceX report definitively answers that question. First, let's look at the demand side. 43.5% of users state they adopt embedded financial services simply because of speed and efficiency. It removes the friction of having to pause a purchasing journey to go start a separate banking journey. Consumers fundamentally prefer to finance the car while they are looking at the car.

But the supply side numbers are the real wake-up call for the industry, aren't they?

They are staggering. 58.3% of financing providers and a massive 80% of investing providers view banking as a service, or BaaS, as Actively economically relevant and revenue generating right now.

This isn't a 5-year projection.

No, this is not a future projection. One participating bank in the study reported growth from these embedded channels of 70% in 2024, and they're projecting another 50% growth in 2025.

Here's where it gets really interesting for you, the financial professional listening to this. If you're sitting inside a legacy institution, this is where you need to take notes. Embedded finance can no longer be treated as a niche project managed by a small team in a digital sandbox.

No. be treated as a serious core distribution strategy.

Right. It is your new route to market. It builds stronger deposit franchises and allows for incredibly precise targeted lending. Yeah. Because you are leveraging the contextual data of your partner platforms.

The risk is no longer that a nimble fintech is going to destroy your bank. The real existential risk is that your bank fails to build the necessary infrastructure to become the partner of choice for the brands and platforms that actually own the customer's daily attention.

If you cannot embed your services into their environment seamlessly, you will simply be locked out of the next generation of loan origination.

Precisely.

But, you know, this beautiful vision of a bank sitting invisibly inside a supermarket app or a ridesharing app, it hits a massive structural brick wall the second you realize the sheer volume of data that has to cross securely between those 2 companies.

Oh yeah, the data plumbing.

The plumbing to do this safely does not exist by default. You cannot have a retailer originating your loans if the systems cannot talk to each other perfectly, securely, and legally.

Which brings us to the great enabler of this entire ecosystem. The invisible bank is entirely dependent on data interoperability. We have to talk about open banking, the maturation of open finance, and how data itself is becoming a regulated infrastructure.

The scale of this data movement is, it's honestly incredibly difficult to wrap your head around. The magazine cites statistics from the Open Banking Limited 2025 Impact Report. In the UK alone, there were 16.5 million open banking user connections in 2025.

And those connections generated 24 billion API calls.

Wait, 24 billion? With a B?

24 billion with a B. That is a 27% increase from the previous year.

That is insane. When we throw around terms like 24 billion API calls, it is very easy for the brain to just tune it out as abstract technology jargon. But we really need to ground that number in reality to understand the magnitude of what is happening. An API, an Application Programming Interface, is essentially a digital doorway that allows 2 different software systems to talk to each other securely.

Right. So let's break down the exact microsecond lifecycle of one of those API calls. What is actually happening?

Yes, walk me through it.

In the context of open banking, an API call is a micro-interaction of trust. Let's go back to our Sainsbury's and NatWest example. You're in the app and you want to use a new embedded lending product. When you click that button, the supermarket software fires an API call to the bank's server.

Okay.

In a matter of milliseconds, it is asking, can you cryptographically confirm this person's identity? Can you verify they have sufficient income history for this loan? And do we have the explicit digital consent of the user to access this data?

And the bank responds.

The bank system receives the call, verifies the permissions, pulls the data from that core ledger we talked about earlier, packages it securely, and sends it back to the supermarket app.

All in the time it takes you to blink.

Exactly. Now, multiply that micro-interaction of trust by 24 billion. That is the volume of data moving between third parties and banks in just one country. Open banking has moved far beyond being a nifty feature for tech enthusiasts. It is now critical national infrastructure.

If those APIs go down, the modern digital economy halts.

It literally stops.

And this concept is expanding aggressively across Europe through new regulatory frameworks. The text specifically highlights the Financial Data Access Framework, known as FIDA, and the evolution of the Payment Services Directive into PSD3. These are not just technical updates; they are profound philosophical shifts in how the law treats financial information.

FIDA and PSD3 are essentially turning financial data into a highly portable, highly regulated asset. Historically, the legal and practical reality was that a bank owned the data sitting in its vault. If a bank knew your transaction history, your exact salary, and your risk profile, that data was their proprietary moat.

It was the crown jewel that prevented you from easily moving to a competitor.

Right.

So if I put myself in the shoes of an old-school banking executive looking at these new regulations, I would be terrified.

Many are.

Right? If regulators are forcing me by law to build these API doorways and make my customer data easily portable, aren't they just forcing me to give away my crown jewels to my Competitors in these new tech platforms. Why on earth would I want to participate in this ecosystem?

It is a very common, very understandable fear. But the Finance X piece clarifies why that defensive posture is a strategic dead end. Institutions that view open finance purely as a massive compliance burden, the banks that only build the APIs because the law forces them to, and who expose their data as reluctantly and clunkily as possible, They are going to be completely disintermediated.

They will become the dumb pipes they fear so much.

Exactly.

So, who wins?

The institutions that treat open data portability as a strategic capability. Because the rules of the game have changed. The game is no longer about hoarding data in a silo. The game is about building new propositions around trust, consent, and intelligence.

Okay, what does that look like?

If your bank can ingest a customer's data from multiple external sources— their investment accounts, their retail spending, their mortgage at a different bank— and use your orchestration layer to provide them with superior actionable insights, you become their primary financial hub.

You win their loyalty by being the smartest node in the network, not by having the thickest vault door. It is about transparency and utility.

Precisely. And speaking of networks that have had to learn brutal lessons about trust, transparency, and data integrity, the magazine draws a fascinating parallel to a completely different sector of finance that is undergoing the exact same maturation process.

Oh, the crypto infrastructure space.

Yes.

This is such a great comparison because the crypto industry went through an incredibly chaotic, rebellious adolescence, and now it is slamming face-first into the realities of regulation. The magazine features an interview with Sean Murphy regarding Paybis, which perfectly illustrates this.

Paybis is a crypto infrastructure business, and the fact that they just celebrated their 12th anniversary is a massive milestone in an industry known for burning out companies in months.

12 years is like a century in crypto time.

It really is. They have grown to 200 employees. They are not a scrappy, anonymous startup operating in the shadows of the internet anymore. They are building the heavy enterprise-grade plumbing that fully licensed banks, massive payment institutions, and corporate clients use to interact with digital assets securely.

And Enikandze Zubarev, the CEO, makes a profound observation about the cultural shift in the industry. He notes that the era where crypto sold the Absence of rules as a feature is completely irrevocably dead.

That statement encapsulates the entire maturation of the market. For years, the foundational marketing pitch of early cryptocurrency was the ability to bypass the traditional financial system. It was about avoiding central bank regulation, obfuscating identities, and operating entirely outside the purview of the state.

Right. The Wild West.

But as the technology has tried to integrate with the broader economy, reality has set in. Institutional capital, the pension funds, the massive asset managers, they do not invest in systems without rules. They require institutional safeguards.

The article explicitly points to the new regulatory hammers that are forcing this compliance. We're talking about MiCA, the Markets in Crypto-Assets Regulation in the European Union, and the Genius Act in the US, along with new stringent frameworks in hubs like Hong Kong and Singapore. But, um, how do these frameworks actually impose rules on systems that we're fundamentally designed to be decentralized.

Mechanically, these regulations target the on-ramps and off-ramps. They target the infrastructure providers like Paybis, the exchanges, and the custodians. MiCA, for example, forces these entities to adhere to strict consumer protection standards, transparency requirements, and operational resilience mandates.

So they have to act like banks.

Exactly. It forces them to implement the exact same know your customer, or KYC, and anti-money laundering AML protocols that a traditional bank uses.

It strips away the anonymity. And the brutal truth of the market over the last few years, the so-called crypto winter, is that the firms that complained the loudest about these regulations, the ones who tried to fight the tightening rules and cling to the Wild West mentality, they have largely evaporated.

Yeah, they were wiped out by fraud, mismanagement, or regulatory enforcement.

The survivors, the companies that are actually thriving today, are the ones who embraced the regulations. They put their heads down and focused on building what Zubarev calls the boring, trustworthy plumbing. They didn't view compliance as an enemy. They integrated regulatory reporting directly into their product architecture as a core feature.

So the actionable lesson here for you listening is universal, whether you are managing open banking APIs at a legacy bank or building a new digital asset ledger. Data sharing, interoperability, and absolute compliance are no longer optional.

You cannot hide behind your walls and you cannot operate in the shadows.

No. Trust and transparency are the new unassailable competitive advantages. If you build systems that regulators love to audit and consumers fundamentally trust, you will win the infrastructure war.

And that brings us to an area where this need for data interoperability, trust, and intense regulatory scrutiny are colliding in a way that is causing massive systemic headaches across the entire global financial sector. Because the most complex, high-stakes data that banks now have to manage, ingest, and report on is no longer just financial data.

It is sustainability data.

And I want to pause here to emphasize just how radically the tone has shifted on this topic.

Yeah.

If we rewind a few years, ESG— environmental, social, and governance criteria— was essentially treated as a public relations exercise.

It was corporate communications. It was soft.

Right. A bank would issue a green bond, they would fund a tree-planting initiative, They would put a beautiful high-resolution photo of a wind turbine on the COVID of their annual report, and the board would call it a day. It was a soft marketing layer placed on top of existing products to make the brand look responsible.

But as the FinanceX articles detail with incredible urgency, sustainable finance has entered a mature, highly consequential, and heavily regulated phase. The markets, the central banks, and the regulators have entirely lost their patience with vague, unsupported marketing claims.

ESG is no longer a brochure.

No, it is being hardwired directly into the core product architecture and risk modeling of the institution.

The text highlights the 2025 European Banking Authority, or EBA, guidelines. And these guidelines are not polite suggestions; they legally mandate that ESG considerations must be moved out of the marketing department and directly into the core, mechanical functions of the bank: governance, risk management, credit assessment, and capital planning.

This is the decisive structural shift. We need to look at the real-world examples provided in the text to understand the mathematical impact this has on everyday banking. Let's take mortgage lending, which is the bedrock of most retail banks.

Okay.

Historically, the mechanics of underwriting a mortgage were straightforward. The bank looked at your verifiable income, your credit score, the amount of your down payment, and the appraised market value of the property. Based on those numbers, they calculated the risk of default and offered you an interest rate.

Pretty standard.

Yeah.

But under these new EBA frameworks, that mathematical model has to change, right? Mortgage lending increasingly must factor in the building's actual energy performance.

Yes, because energy performance is no longer just an environmental concern. It is a material financial risk. If a bank originates a 30-year fixed-rate mortgage on a house that is terribly energy inefficient, terrible insulation, ancient heating systems. What happens to that borrower in 5 years when carbon taxes are implemented or global energy prices spike massively?

Oh, wow. The borrower's monthly utility bills skyrocket, which destroys their debt-to-income ratio, which means they might default on the mortgage.

Exactly.

So the carbon footprint of the house directly impacts the probability of default on the loan.

Exactly. Or consider SME finance lending to small and medium enterprises. Banks are now required to model the climate transition exposure of the businesses they lend to. Let's say a bank is assessing a loan application from a regional logistics company. This company owns a fleet of 200 diesel trucks.

Right.

The bank's risk model now has to calculate what happens to that company's cash flow when new municipal emissions regulations ban diesel trucks from entering major city centers in 3 years.

The logistics company would have to spend millions to upgrade to an electric fleet, which could bankrupt them. Which means they default on the bank loan. So the bank has to price that specific climate transition risk into the interest rate of the loan today.

But to price that risk accurately, the bank's mathematical models need data. And this introduces arguably the biggest operational nightmare in modern banking: the ESG data gap.

Every professional listening to this who deals with compliance or risk is probably nodding their head right now because the data gap is Terrifying. You are asking a bank to calculate risk, but the data they need to do it is a complete mess. As the magazine points out, sustainability reporting frameworks are incredibly fragmented across different jurisdictions.

It's chaotic.

What counts as green in France might not count as green in Germany.

And the data on corporate supply chains is often incomplete, unverified, or entirely reliant on self-reported estimates. The emissions methodologies differ wildly depending on which consultant you hire.

To put a metaphor on this, it is like trying to measure the emotional weight of a novel using a kitchen scale.

That's a great way to put it.

You are using the wrong tools to measure a fundamentally different type of material. You are trying to combine perfectly precise, mathematically sound financial data like the exact yield on a 10-year Treasury bond with incredibly messy, unstructured, non-financial data like the estimated Scope 3 carbon emissions of a clothing manufacturer's supply chain And we should clarify Scope 3 for a moment because it is the hardest part of this equation. Please do.

Scope 1 emissions are what a company burns directly, the gas in their own trucks. Scope 2 is the electricity they buy to keep the lights on. But Scope 3 is the carbon footprint of their entire external value chain.

Ah.

It is the emissions created by the suppliers who make their raw materials and the emissions created by the consumers who eventually use their products.

Calculating Scope 3 is essentially an exercise in highly educated guessing. Yet, the regulators expect banks to take this messy, estimated Scope 3 data, merge it with their pristine financial data, and put it into a decision-making model that is explainable to an auditor.

This is where we need to look at the insights from Matthew Barnard. He's the executive director at BBD. He frames the mechanical challenge perfectly. He says the issue facing banks is no longer just about collecting ESG data. There are plenty of data vendors out there now.

Right.

The real existential challenge is building the IT architectures capable of integrating high-volume, highly variable sustainability data into those legacy operational systems we talked about in the very beginning. Remember the mainframes?

Right. The legacy COBOL mainframe understands dollars and cents. It is a relational database built in 1985. It has fields for numeric currency. It does not have data fields for unstructured text explaining the biodiversity impact of a mining operation or the carbon equivalency metrics of a diesel fleet.

No, it doesn't.

If you try to force that unstructured data into the legacy ledger, it literally breaks the architecture.

You are trying to force non-financial metadata through financial plumbing. And you have to do it while maintaining absolute governance, security, and auditability. Barnard argues that sustainability data must be treated with the exact same reverence as core payment data.

It requires the same level of architectural rigor.

Yes, the same API-led integration strategies we discussed with open banking. And crucially, it requires lineage tracking.

Lineage tracking. Let's explain the mechanics of that. What does that actually mean for the bank?

Lineage tracking means that when a bank produces a report that says, this portfolio has a low climate transition risk, the regulator can point to that conclusion and say, prove it. Lineage tracking is the digital breadcrumb trail.

Okay, so it shows the steps.

Exactly. It shows exactly where the raw data came from, which specific vendor supplied it, what mathematical transformations or assumptions the bank's algorithm applied to it, and how it resulted in that final number.

The biggest takeaway from Barnard's insight is a necessary acceptance of imperfection. One of the most important shifts happening right now in compliance is the realization that perfect, pristine ESG data is a myth.

It really is.

It may never exist. You are never going to have a satellite tracking every single carbon molecule emitted by a global supply chain So, what is the actionable lesson?

Do you just wait on the sidelines for the data to get better?

No. The winners in the next decade will be the institutions that can intelligently integrate and operationalize imperfect data.

They will build adaptable digital foundations.

Yes, like the orchestration layers we discussed earlier, that can ingest diverse, messy data streams, apply standardized risk models, track the lineage of how that data was interpreted, and confidently defend those interpretations to a regulator.

If you can prove how you arrived at a conclusion using the best available data at the time, time, you are in a much safer position than an institution making broad, generic claims they cannot mathematically trace.

If we connect this to the bigger picture, the data gap is scary, but having a defensible process is the shield. Which brings us to a very scary reality for the people tasked with defending those claims, and our final area of focus: the regtech reckoning and the massive legal weight of greenwashing.

If you synthesize everything we have discussed so far, The operational burden is staggering. You have embedded finance spreading your brand and your products across dozens of third-party apps. You have open banking generating 24 billion API calls that need to be monitored.

You have complex, imperfect, heavily scrutinized ESG data being hardwired into your core credit risk models. How on earth does a human compliance team, even a team of 1,000 lawyers, keep up with that volume, velocity, and complexity?

The blunt answer is they can't. You cannot solve a 24 billion API call problem by just hiring more compliance officers to read spreadsheets. It is mechanically impossible. Right. And that is why regtech, regulatory technology, is completely redefining how compliance operates in European financial services. We are moving away from manual audits and moving toward the use of artificial intelligence and automated systems for continuous risk identification.

The insights from Nicholas Kalikiris at DLA Piper are highly relevant He points out the reality for banks with cross-border operations. Regulatory requirements are no longer static, they're a constantly moving target. You have dozens of different national authorities, different legal systems, and different languages, all updating their rules, their reporting formats, and their capital requirements continuously.

It's an impossible task for a human.

I want to use another analogy here to explain how RegTech actually solves this. Imagine you were in a massive room full of screaming diplomats from 50 different countries, all shouting new laws at you at the same time.

Okay, stressful.

Historically, compliance was like having one poor translator trying to write down everything they said and then running down the hall to tell the engineering team to change the code.

Right, and RegTech acts as an automated, universal translator that is hardwired directly into the building's intercom system.

Exactly. So mechanically, how does this Modern regtech uses natural language processing AI. It can ingest a 400-page regulatory directive written in German, parse the legal text, understand the specific operational mandates, and systematically map those new external rules directly to the bank's internal policies and control frameworks.

It provides a massive integrated digital overview. So when a specific consumer protection rule changes in Germany on a Tuesday, The regtech system automatically flags the exact internal processes and the specific lines of code that need to be updated by the compliance officer sitting in the Spanish branch on Wednesday.

Wow.

It shifts the entire compliance posture from a reactive, manual audit process, where you only find out you broke a rule 6 months later, to a proactive, continuous, automated capability.

And institutions desperately need that automated capability right now, because there's a massive legal trap waiting to spring on anyone who isn't paying attention. And it specifically centers around greenwashing in digital finance. This is where the rubber meets the road on everything we've talked about regarding sustainability data and embedded finance.

For a long time, greenwashing was primarily viewed as a reputational risk. If an environmental NGO caught your bank exaggerating the impact of a green loan, you might suffer a bad news cycle. You'd get a negative article in the financial press, maybe a small fine, and you'd promise to do better.

Slap on the wrist.

But as the Finance X magazine explicitly warns, that era of leniency is completely over. Sustainability claims on apps, websites, and digital onboarding journeys are no longer viewed by regulators as marketing fluff. They are now considered legally binding parts of the consumer's economic decision-making process.

Let's break down exactly what this means in practice, because the legal liability here is shocking. Let's say a bank has a beautiful, sleek mobile app. And next to a specific investment fund or a new mortgage product, the marketing team decides to put a little green leaf icon, or they use the phrase climate-friendly.

In the eyes of the new regulatory frameworks, specifically the EU Directive 2023/2673, which governs the distance marketing of consumer financial services, and Directive 2024/825, which focuses on empowering consumers for the green transition, that little green leaf icon is no longer just a graphic design choice. It is a contractual representation.

Wait, really? A tiny icon? Yes.

If a consumer chooses that investment fund because of that green leaf, and a regulator subsequently asks the bank to prove why that product is green, the bank cannot just point to a vague corporate policy. They must provide auditable, material, data-driven lineage tracking to back up that specific claim.

And if they can't?

If the bank cannot produce that data, they have legally engaged in an unfair commercial practice.

And the text notes that local transpositions of these massive EU directives are already hitting the books and being enforced. For instance, in Romania, Law No. 363/2007 on Unfair Commercial Practices has been specifically amended to reflect these new digital realities. You absolutely cannot slap a sustainable label or a green color scheme on a digital onboarding journey without having the hard data infrastructure to defend it in court.

A careless use of sustainability claims by an overeager marketing team can now lead to severe systemic legal liabilities for the entire institution. The regulators are drawing a hard line. If you claim it on the screen, you must prove it in the server.

And as we just discussed at length, wrangling that ESG data into the server is incredibly difficult.

So what does this reality require from the internal structure of a financial institution? It means that traditional corporate silos must be entirely destroyed.

Right.

Historically, the marketing team designed the app interface, the compliance team read the regulations, and the IT team managed the server. and they barely spoke to each other. That model is now legally dangerous.

Because they're all affecting the same risk.

Exactly. The marketing team cannot design a digital interface without being hardwired into the compliance team, who in turn must be hardwired into the ESG data infrastructure managed by IT.

So what does this all mean? If marketing wants to use a green color scheme to imply sustainability, compliance needs to be able to push a button and pull the API lineage data to prove the underlying assets that actually meets the EBA guidelines for transition risk.

It requires total, seamless organizational alignment. And as the piece from Mastercard Poland emphasizes towards the end of the magazine, bridging this gap requires immense collaboration. Bringing together fintech innovation, evolving policy, and market momentum is the only way to scale these solutions safely.

Yeah, no single legacy bank has the capacity to build perfect ESG data models, flawless regtech mapping, and entirely new core banking orchestration layers all by themselves in a vacuum. It requires ongoing dialogue, shared technological standards, and deep cooperation across the entire financial ecosystem.

This is a massive shift.

It is a massive, incredibly complex puzzle. And it brings us to the synthesis of everything we've unpacked today. We started this deep dive looking at the clean, binary X-ray of a traditional bank— a self-contained building that owned everything.

Right.

And over the last hour, we've watched that simple structure dissolve into an incredibly complex, highly regulated, interconnected nervous system. We went from the infrastructure arbitrage of placing operating layers like Core Ignite on top of legacy mainframes to the realities of embedded finance, distributing NatWest loans in the produce aisle of Sainsbury's.

We covered a lot of ground.

We really did. We broke down the mechanics of 24 billion API calls, The terrifying challenge of hardwiring messy Scope 3 ESG data into mathematical credit risk models. And finally, the severe legal realities of regtech and the liability of a green leaf icon.

If you step back and synthesize all of these distinct mechanisms, you realize that the fundamental definition of what constitutes a bank is changing in real time. For centuries, the defining question of a financial institution, the metric of its power, was simply, who owns the balance sheet? Today, the balance sheet is increasingly becoming a commoditized utility. The new question, the question that will absolutely determine who survives and who thrives in the next decade is, who controls the customer experience and who controls the flow of trusted, regulated data surrounding it? The bank of the future is no longer a vault. It is an orchestrator of trust within a much wider digital ecosystem.

And that leaves me with a final provocative thought for you, the listener. To mull over as you close this out and go back to your day. Let's assume you execute everything we talked about perfectly. You build the orchestration layer, you master the APIs, you integrate the ESG data, and you deploy the regtech.

You do it all!

We are looking at a future where your banking services become a flawless, completely invisible layer. You are perfectly embedded into other brands' platforms, underwritten by algorithms, and operating silently in the background. It will all work beautifully. But here's the paradox for executives: as a financial institution, how do you maintain any semblance of brand loyalty when your ultimate goal is to become invisible?

That is the big question.

If the ultimate success of embedded finance means that your customer never, ever steps foot in your physical branch or actively visits your digital website again, if they interact with the supermarket, the ridesharing app, and the accounting software, but never directly with your brand logo, Mm-hmm. What exactly is your relationship with that customer in the year 2030? Are you a brand they actually love and trust, or have you engineered yourself into being nothing more than the silent, replaceable engine humming in the basement of the internet?

The clean lines of the X-ray are truly gone. The boundaries are gone.

They really are. Welcome to The Nervous System. Thank you so much for diving deep with us today into the 23rd edition of Finance X Magazine. It has been a phenomenal, complex journey, and we hope you walk away with the blueprint you need. We will catch you on the next deep dive.