Latest / Fintech Conversations with Fexingo: Banking, Payments, and Financial Software Companies / How Open Banking Is Rewiring Consumer Wallets
Transcript
- Lucas: For the last decade, the biggest bet in fintech was that we would all have one app to rule them all. Mint, then Robinhood, then Chime—everyone wanted to be the single dashboard where you checked your checking account, your mortgage, and your crypto holdings. But if you look closely at the transaction data right now, that dream is fracturing. We are seeing a move away from pure visibility toward actual action. Luna: Right, and that’s because reading your balance doesn’t feel like much of a product anymore. Everyone has that. The real moat is being able to move the money without logging into the bank's clunky portal. Lucas: Exactly. We used to talk about account aggregation as a passive feature—a nice to have for budgeting apps. Now, with the rise of Payment Initiation Services, or PIS, the conversation has shifted to write-enabled access. You aren't just watching the water; you're turning the tap. This is what regulators in Europe have been pushing under PSD2, but in the United States, it’s happening through market forces rather than mandate. Luna: So it’s less about government policy here and more about companies like Plaid and Stripe building the pipes that make those transfers possible? Lucas: Precisely. Let’s look at Plaid. They’ve essentially become the universal translator for American finance. Before their API layer, if you wanted to link a user’s Chase account to your budgeting app, you needed direct integrations with thousands of banks, each with different security protocols and document formats. Plaid standardized that handshake. And now, they’re expanding beyond just pulling data to actually initiating payments on behalf of the user. Luna: That feels risky though. If an app can pull my balance, I get it. But if it can initiate a payment, isn’t that opening up a whole new vector for fraud? Lucas: It is a valid concern, which is why the liability framework is so critical here. Under current rules, if a fraudulent transaction happens on a credit card, the issuer absorbs most of the loss. With open banking payment initiation, the liability often shifts to the originator—the fintech company or the merchant facilitating the transfer. This creates a massive incentive for these new players to build better fraud detection than the legacy banks ever did. Luna: Because if they mess up, they pay out of pocket? That changes their risk calculus completely compared to the old model. Lucas: It does. Take Stripe Financial Connections as another example. They are embedding this capability directly into checkout flows. Imagine buying groceries or paying a utility bill, and instead of entering card details, you authorize the payment directly from your bank account via an open banking protocol. It’s faster for the consumer, cheaper for the merchant because there are no interchange fees, and the money moves instantly. Luna: And instantly is the keyword here. ACH takes days. Cards take days. Direct bank pulls are near real time. That speed advantage is huge for cash flow management. Lucas: Yes, especially for small businesses. But let’s zoom out to the consumer side for a moment. Why hasn’t this taken off fully in the US yet? In Europe, it’s baked into the regulatory DNA. Here, we rely on voluntary participation from banks. Some big ones like JPMorgan or Bank of America are hesitant to expose their customer base to third-party apps because they fear disintermediation. They don’t want you using their app to send money elsewhere. Luna: So they’re protecting their own engagement metrics by making the APIs harder to use or less reliable? That sounds like classic incumbent behavior. Lucas: Spot on. There have been reports over the last few years where major banks degraded their API performance during peak times or added extra friction to third-party login attempts. It wasn’t always malicious, sometimes it was just technical debt catching up, but the effect was the same. It slowed down the innovation cycle. However, pressure from the Consumer Financial Protection Bureau is starting to bite. Luna: The CFPB is finally weighing in on data portability? I thought they were more focused on predatory lending practices. Lucas: They are, but those two things are linked. If you can’t easily move your data or your money, you’re stuck with whatever bad service your current bank provides. Portability is the ultimate competitive lever. The CFPB’s recent guidance suggests they want to ensure consumers can exercise their right to share data without unnecessary barriers. This isn’t just about convenience; it’s about market efficiency. Luna: I guess I hadn’t thought about it that way. It’s basically antitrust logic applied to digital wallets. If I can leave instantly, the bank has to treat me better. Lucas: Exactly. And this is where the neobanks are winning. Companies like Chime or SoFi didn’t start with branch networks. They started with better UX and lower fees. As open banking matures, even the biggest legacy banks will have to offer similar ease of movement, or they’ll lose the best customers to apps that do. It’s forcing a democratization of banking features. Luna: But what about the privacy angle? When you give Plaid or Stripe access to your transaction history, who else sees it? Are they selling that data? Lucas: That’s the billion-dollar question. The terms of service usually state that data is used strictly for the service provided—linking accounts or processing payments. They generally don’t sell raw transaction data to advertisers. However, they do aggregate anonymized insights to help banks understand spending trends. The risk isn’t really identity theft; it’s profiling. If a lender knows exactly what you spend on dining versus savings, they can price your loan differently based on behavioral data, not just credit score. Luna: Dynamic pricing based on lifestyle. That feels a bit dystopian if it’s not transparent. Do consumers even realize that’s happening? Lucas: Most don’t. And that’s the governance gap. We need clearer standards around what constitutes 'necessary' data sharing versus 'optional' enrichment. Right now, to use a budgeting app, you might be granting access to every single transaction detail, including medical payments or charitable donations. That granularity is dangerous if the security layer fails. Luna: So the technology is ahead of the consent model. We’re giving away keys to the house because the app looks shiny. Lucas: Precisely. And as the ecosystem grows, we’re going to see more specialized players emerge. Not just general aggregators, but vertical-specific ones. Think about health-tech apps that need to verify income for insurance purposes, or proptech platforms that need to verify rental history. Each of these will require its own secure channel, further fragmenting the infrastructure. Luna: Fragmentation seems inevitable. But does it make the system more robust or just more complex to audit? Lucas: Complexity is the enemy of security. If there are ten different ways to authenticate a payment initiation, a hacker only needs to find one weak link. This is why industry-wide standards are crucial. The FDX Forum, led by major banks, is trying to create a unified standard called Account Information Service and Payment Initiation Service protocols. If everyone adopts the same encryption and authentication methods, the attack surface shrinks significantly. Luna: So collaboration between competitors is actually driving security up? That’s counter-intuitive but makes sense. Lucas: It does. Competition happens at the product layer—how you present the data, how you advise the user. But the plumbing needs to be uniform. Otherwise, we end up with a patchwork quilt of proprietary APIs that are easy to break into. The goal is a public utility model for finance data, where the rails are safe, and the cars on the rails can vary wildly. Luna: I like that analogy. Public roads, private vehicles. As long as the road is paved well, anyone can drive. Lucas: Well said. And honestly, if today was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. Luna: Yeah, supporting the show keeps us digging into these structural shifts rather than just chasing headlines. Lucas: Let’s bring it back to the consumer experience for a second. If you were designing the ideal banking interface for someone in twenty twenty-six, what would it look like given this open banking reality? Luna: I’d say it wouldn’t look like a bank app at all. It would look like a command center. You wouldn’t log in to check balances. The data would stream in passively from wherever you hold money. Lucas: Passive aggregation. So the friction disappears entirely. You’re not managing accounts; you’re managing liquidity. Luna: Exactly. And the default option for any payment would be direct bank transfer, because it’s cheapest and fastest. Card networks would become a fallback for situations where you need chargebacks or rewards points. Lucas: Which flips the entire revenue model of the payment industry. Visa and Mastercard built empires on interchange fees. If open banking makes direct bank payments the norm for peer to peer and merchant transactions, those fees evaporate. They’ll have to pivot hard to cross-border or premium reward ecosystems. Luna: Or they’ll try to lock you in with exclusive perks that only work on their network. It’s going to be a tug of war between the openness of banking rails and the closed loops of reward programs. Lucas: That tension is fascinating. On one hand, you have the regulatory push for openness and competition. On the other, you have the commercial incentive to create walled gardens that extract maximum value from loyal users. Which force wins out depends on how much consumers care about their data versus their rewards. Luna: I think younger demographics are tipping toward openness. They’ve grown up with digital identities and don’t have the same attachment to physical branches or legacy brands. Lucas: True. But older demographics, who control the bulk of wealth, are slower to adopt. Banks know this. They’re betting that once people are comfortable with the basic infrastructure, they’ll gradually unlock more advanced features. It’s a slow burn, not an explosion. Luna: Slow burn is probably safer anyway. We saw what happened when crypto moved too fast. Stability matters in finance. Lucas: Absolutely. The future of open banking isn’t about disrupting the system overnight; it’s about quietly rewiring it until the old doors are locked and the new ones are wide open. The question remains whether legacy banks will adapt before they become irrelevant utilities.