Curiosity Code Podcast

The episode surfaces a few non-obvious points - agentic-first design as the successor to API-first, and data governance as the first infrastructure question - but is padded with general fintech narration, repeated 'table sticks' metaphors, and platitudes about change management. The insight-to-filler ratio is mediocre for a 32-minute runtime.

“now it's all about being agentic by default by native. Thinking about how can you make sure you build something that also thinks about two consumers”

“How's your infrastructure and how is your data governance? Because you cannot scale in a business without a strong foundation and infrastructure”

The three-phase framing (batch → open banking APIs → embedded/agentic) is a useful mental model, but everything else - PSD2 as forcing function, real-time as table stakes, build-vs-partner via the Uber/Stripe analogy - is well-worn fintech commentary. The 'agentic first' framing is genuinely early but never developed into a concrete argument.

“The first phase being files. The second phase being the regulatory open banking where banks were opening up for their uh, AIs and PIs data... And then the third phase being truly embedded”

“Uber is an infrastructure for you to go to a 2B but they don't have to become a payments provider. They partner with Stripe”

Christie Kristensen is a genuine practitioner - CMO at Aya (a Nordic open banking aggregator), partnerships roles at MasterCard and World First, now in integration services at Danske Bank - giving her cross-stack fintech credibility. However, she is a senior marketing and partnerships leader, not a founder or technical architect who built settlement infrastructure at scale, which caps the depth of operational specificity she can offer.

“I joined Densky bank last year after I have been at MasterCard and I come with a backpack of experience in the API economy”

“I was at Aya, which was one of the first aggregators and open banking players in the Nordics, where I was the chief marketing officer”

The episode names real companies (Aya, Danske Bank, MasterCard, Stripe, Citi, JP Morgan), a specific regulation (PSD2), and one concrete product origin story (Spier app), but offers zero quantitative data - no adoption metrics, no cost figures, no latency benchmarks, no revenue numbers. Examples function as name-drops rather than as evidence for any claim.

“a fun anecdote is that Spier, the money app that was the backbone of the Aya company, the aggregator that I worked with was because of that pain point of the founder wanting to understand their personal financial health”

“coming from MasterCard, looking at our API products and services globally across hundreds of product offerings”

The host lands a few genuinely sharp questions - the red-flag/walk-away question and the build-vs-partner framing are good practitioner prompts - but consistently lets vague answers pass without follow-up, affirms with 'Love it. Great perspective,' and never pushes back on unsubstantiated urgency claims like 'they need to do it this afternoon.' The episode stays friendly rather than productive.

“What's the red flag answer that would make you walk away if you ask question uh, about risks”

“should smaller players even try to build real time infrastructure or is this the moment they admit they need to become middleware on top of bigger uh, Rails”