With us today is Nikolai Braiden, a distinguished FinTech expert and an early pioneer in blockchain technology. He has built a career advising startups on navigating the complex digital landscape, championing technology’s power to innovate financial systems. We’re diving deep into the often-oversold dream of embedded payments, exploring the operational pitfalls that can turn a promising revenue stream into a costly distraction. Our conversation will touch on the harsh realities behind optimistic business cases, the underestimated complexities of compliance and user experience, and the critical strategic mindset required to succeed where others have quietly failed.
You described a case where a projected €1.4 million profit fell by 65% due to unforeseen realities. Beyond slow adoption, what specific hidden costs, like chargebacks or reconciliation, most often surprise leadership, and how can they model these more realistically from day one?
It’s a classic trap, and I’ve seen it happen repeatedly. Leadership gets mesmerized by that shiny 40 to 50 basis points on payment acceptance and builds a beautiful financial model. But they forget that payments are a messy, operational business. The silent killers are always the ones they don’t model properly. Chargebacks are a huge one; they don’t just reverse revenue, they come with fees and can damage your reputation with payment networks. Then there’s foreign exchange; if you’re operating across Europe, what looks great in one country’s currency can get eaten alive by conversion costs. But the most underestimated cost is reconciliation. Your finance team, which was running a smooth ship, is suddenly buried in tracking down declined transactions, managing refunds, and handling disputes. That €1.4 million profit projection looks fantastic on a slide, but when you factor in the operational drag and those thinning margins, it can plummet to a fraction of the initial NPV, just like in the example.
With regulations like PSD3/PSR increasing scrutiny, you mentioned partners can handle compliance at a cost. How should a company evaluate the trade-off between outsourcing full compliance versus developing in-house expertise to better protect margins and user experience?
That’s the million-dollar question, isn’t it? The temptation to offload all compliance is immense because the alphabet soup of PCI, KYC, AML, and card scheme rules is intimidating. A partner can indeed offer you a turnkey solution, but it’s never free. That cost directly erodes your margins, which are likely already thinner than you projected. I’ve also seen partners push for a full-program compliance burden on a company that isn’t even a regulated entity, adding unnecessary cost and complexity. The real danger, especially with new regulations like PSD3/PSR, is that if you fully outsource, you lose touch with a critical part of your business. You risk becoming a simple pass-through, and if the regulator decides your activities blur the line with a licensed PSP, ignorance won’t be a defense. The smart approach is a hybrid one: lean on partners for the heavy lifting initially, but simultaneously build a core competency in-house. This allows you to understand the risks, control the user experience, and negotiate better terms with your partners over time, protecting your long-term strategic interests.
The failure of Coop’s Finance+ app is a powerful example of a “build it and they will come” misstep. What specific customer research questions must a company answer before development to prove their embedded solution solves a real friction point, rather than being just a ‘me-too’ offering?
The Coop story is such a perfect, painful lesson. They had millions of loyal customers, a big brand, and strong partners, but the venture still collapsed in less than a year. The core issue wasn’t the technology; it was a fundamental misunderstanding of the customer. The “if you build it, they will come” mindset is born from internal ambition, not external need. Before writing a single line of code, you have to go out and ask your customers pointed questions. How do you get paid today? What does that process feel like? Where are the delays, the frustrations, the moments you wish were simpler? What are you paying for your current solution, not just in fees, but in time and effort? If your answer to “why would they switch?” is just “because it’s integrated,” you’ve already lost. You need to uncover a genuine pain point—missed payments, complex reconciliation, high transaction fees—that your solution directly and elegantly solves. Otherwise, you’re just another app in an already crowded market, and customers will see no compelling reason to change their ingrained habits.
You highlighted that a poor user experience, like a clunky refund process, can quickly erode trust. What are the key metrics or user feedback channels you recommend teams use post-launch to rapidly identify and fix these friction points before they damage the brand?
This is where treating payments as a product, not just a feature, becomes absolutely critical. A poor user experience is a silent brand killer. You can’t just bolt on a payment UI and call it a day. The most immediate metric to watch is transaction decline rates. A high rate isn’t just lost revenue; it’s a signal that something in your flow is broken or confusing. Another key area is the refund and dispute process. I always tell teams to measure the time-to-resolution for customer issues. A clunky, multi-step refund process creates immense frustration and erodes trust faster than almost anything else. You should have direct feedback channels, like simple post-transaction surveys or an easily accessible support chat, to capture qualitative data. The goal is to create a tight feedback loop where you’re not just looking at dashboards but are actively listening to the user’s voice to identify and smooth out that friction before it becomes a reason for them to leave.
When choosing between models like a simple referral and a full Payfac, what are the most critical strategic questions a leadership team should ask about long-term control and brand identity, rather than just focusing on the initial investment and speed to market?
Teams get fixated on the short term. They want a “quick and easy” integration to test the waters, so they gravitate toward a simple referral model. The problem is, that initial choice can lock you into a path that’s misaligned with your long-term goals. The critical question leadership must ask is: “Five years from now, is payments a core part of our value proposition or just a bolt-on service?” If the answer is that it’s core to your strategy, then you need to think about control. A referral model gives you almost no control over the user experience or the data. A full Payfac model, while complex and expensive upfront, gives you complete ownership. The other key question relates to brand identity. Do you want your customer’s payment experience to be with your brand, or are you comfortable sending them to a third party? That decision has a profound impact on customer trust and your ability to create a truly seamless, integrated product. Focusing only on the initial investment is like choosing a foundation for a skyscraper based on the price of a shed.
Your core advice is to treat payments “as a business, not a feature.” Can you walk through the key organizational changes this requires? For instance, what new team roles or KPIs are essential to manage payments as a successful, standalone business unit?
This is the most important mindset shift, and it has to come from the top. When you treat payments as a feature, it’s a task for the finance or tech department. When you treat it as a business, you recognize you’re effectively entering a brand-new market. Organizationally, this means you need a dedicated product manager for payments—someone who lives and breathes the customer journey, the competitive landscape, and the P&L of the payment product. You also need dedicated operational support to handle the inevitable increase in disputes, refunds, and treasury complexities. You can’t just dump this on your existing teams. The KPIs also have to evolve. Instead of just tracking total processed volume, you need to start measuring things like net revenue per transaction, customer adoption rate against your total addressable volume, and the cost of your payment operations. You begin to manage it like any other business unit, understanding that the early phase may have poor economics, but you’re investing, iterating, and staying the course for the long-term strategic prize.
What is your forecast for the future of embedded payments?
My forecast is one of strategic divergence. The initial gold rush, where every SaaS platform felt they had to bolt on payments, is coming to an end. We’re going to see a split. On one side, you’ll have companies that jumped in without a clear strategy, who will find the thin margins and operational headaches aren’t worth it, and we’ll see more quiet retreats and shutdowns, much like Coop’s. On the other side, you’ll have companies that truly treat payments as a core business. These are the ones who will succeed spectacularly. They won’t just offer payments; they’ll use their unique position and data to solve deep-seated industry problems, creating deeply integrated, high-value financial solutions that become massive competitive moats. The future isn’t just about adding a “Pay Now” button; it’s about a fundamental rethinking of how commerce and finance intersect within specific vertical software, and the winners will be the ones who understand that distinction.