Innovate Finance

There are a handful of genuinely useful observations - PSD3's two-bank safeguarding mandate, IBAN discrimination as an operational hazard, and the API-fragmentation paradox - but the episode is padded with high-level generalities and vendor positioning that dilute the useful ideas-per-minute ratio significantly.

“PSD 3 that is mandating that fintech companies, payment institutions, electronic money institutions regulated in the future, safeguard their customer funds not just into one bank but actually in at least two banks”

“Paradoxically more API when you are in the multi banking setup does not make your task easier because everybody has a different take on APIs”

The API-fragmentation paradox (more APIs = more heterogeneity, not less) is a counterintuitive and genuinely interesting point, and IBAN discrimination is underreported; but the vast majority of the discussion recycled standard industry talking points about resilience, SVB, and multi-banking being strategically valuable.

“Paradoxically more API when you are in the multi banking setup does not make your task easier because everybody has a different take on APIs. So there's a different opinionated perspective on how these things should work. Therefore if you have 10 banks you have as many APIs that you need to integrate”

“we joke that part of what we offer to fintechs working with us to connect to banks is also being a bit of a cultural translator sometimes between the developer, uh, API friendly Sprint based way of working of a fintech and the way of working of a bank”

Victor is a VP of Growth at an early-stage startup with a background in consumer packaged goods - he is knowledgeable about his product's market but is not a senior operator who has built payment infrastructure at scale; the conversation functions largely as a vendor pitch rather than a practitioner sharing hard-won operational depth.

“my background is originally in consumer packaged goods. So nothing related to fintechs”

“I've been at numero now for over two years”

The episode includes a few concrete data points - 300-400 engineers at Revolut/Wise, 10x payment cost reduction, 3x IBAN trust from their survey, 20+ integrated banks, named regulators and companies - but key claims lack methodology or sourcing and the survey results are presented without any detail on sample size or date.

“when you are revolut, uh, when you're wise, you've had to build yourself, you've had to have I think between 300 to 400 engineers to build and maintain infrastructure”

“consumers, the end consumers using fintech products would value much more local ibans. Like they trust these local ibans at least three times more than if they see uh, an IBAN that's not in their local markets”

The host asks broad, telegraphed questions lifted directly from a standard fintech interview playbook, never challenges a single claim, and explicitly praises the guest's answers as 'beautiful' - the format is a PR vehicle for Numeral rather than a substantive conversation that tests or sharpens the guest's thinking.

“And can you share with us a little bit about your professional journey and background and how did you find yourself in Numero?”

“That was a beautiful end to our podcast. Thank you so much, Victor”