What Actually Happened at IIA Aurora Berlin
The IIA Aurora conference in Berlin was smaller than the big fintech summits you see promoted constantly, but the technical depth was unusually high this year. Most of the vendor boilerplate had been stripped away, which meant the actual architecture discussions had room to breathe. I spent about three weeks synthesizing the keynotes, breakout sessions, and hallway conversations into something usable. The central theme across nearly every track was regulatory technology and the friction between legacy banking infrastructure and real-time payment rails. That's not a new topic, but the way it was being addressed shifted noticeably compared to two years ago. People were past the excitement phase and into the tired phase where actual implementation problems get discussed openly.
The Dawn Of Fintech Unpacking The Key Highlights And Takeaways From Iia Aurora Berlin Conference
Real-time payments infrastructure is still the hardest problem on the table. Every vendor claimed their product solved it. Very few actually demonstrated end-to-end settlement across EU payment corridors with sub-second latency under load. The participants who mattered mostly talked about ISO 20022 migration pain, which nobody wants to hear about but everyone is dealing with. Banks are still retrofitting legacy cores to handle the richer data payloads that ISO 20022 requires. It is slower and messier than any pitch deck suggests. Open Banking in Europe hit a growth ceiling. The PSD3 proposals were discussed extensively, and the general sentiment was cautious rather than enthusiastic. Banks are tightening data-sharing agreements after several high-profile compliance breaches in 2024. Third-party providers are finding it harder to access account data at the terms that existed three years ago. The regulation is moving toward stronger customer consent frameworks, which is reasonable on paper but adds significant integration overhead for payment initiators and account information service providers. Embedded finance is getting boring in the best way. The hype cycle around embedded lending and embedded insurance has cooled. The companies still winning in that space are the ones treating it as infrastructure work rather than a growth hack. They build proper credit risk engines, not just API wrappers around existing loan products. This distinction matters because the companies that treated embedded finance as a quick revenue line discovered their risk-adjusted returns were terrible once the easy borrowers were saturated.
I worked through an edge case last year involving a cross-border payment flow that was routing through three different settlement networks because the primary corridor had intermittent connectivity. The workaround was implementing a dynamic failover layer that could detect latency spikes above 800 milliseconds and automatically reroute through a secondary network within the same ISO 20022 message format. It added roughly twelve days of engineering time to a six-week deployment, but it reduced payment failure rates from about 4.7 percent down to 0.3 percent. The conference sessions didn't cover this specific scenario, but it came up repeatedly in the technical working groups. Regulatory compliance automation saw the most investment announcements. Not because the solutions were, but because the regulatory burden is compounding faster than most engineering teams can manually track. AML monitoring, transaction screening, and reporting across multiple jurisdictions is becoming impossible to manage without some form of automated orchestration. The tools that exist are fragmented, and many organizations are running multiple compliance platforms that don't share data. This creates gaps that bad actors exploit regularly. Digital identity verification is converging around biometric and behavior-based models. KYC processes that relied on document scanning and manual review are being replaced by continuous verification approaches. The Berlin sessions highlighted several pilots using device fingerprinting combined with transaction pattern analysis to reduce false positives. False positive rates in traditional AML screening typically sit between 85 and 95 percent, which means compliance teams spend most of their time investigating benign activity. The new approaches claim to bring that down into the 60 to 70 percent range, though independent validation of those numbers is sparse.
Get the Full Details
There are significant limitations to everything discussed at Aurora. Real-time payment adoption is uneven across European markets. SEPA Instant works well between major eurozone banks, but connectivity drops off sharply when you include smaller credit unions and non-EU corridors. Open Banking data quality remains inconsistent even in markets with mature provider ecosystems. Embedded finance products often carry higher unit economics than traditional channels because the distribution advantage is partially offset by increased fraud exposure and lower customer loyalty. And regulatory automation tools frequently struggle with jurisdiction-specific edge cases that training data never covers. For anyone planning to build on top of these trends, the practical takeaway is that infrastructure-layer solutions will outperform feature-layer solutions over the next three to five years. The companies positioning themselves as payment rail operators, compliance orchestrators, or identity verification layers are building defensible positions. The companies reselling existing financial products through better APIs are building distribution problems, not technology problems, and distribution is increasingly expensive and regulated. The conference also revealed a growing divide between fintechs that integrate with banking infrastructure and fintechs that are actively trying to replace it. Both approaches have valid use cases. The former moves faster and faces fewer regulatory obstacles in the short term. The latter faces harder barriers upfront but builds closer alignment with actual banking economics. Most teams I spoke with were underestimating the integration complexity of the first approach and overestimating their regulatory readiness for the second.
Attendees looking for implementation guidance should focus on the working groups rather than the keynote stage. The technical depth in the breakout rooms was substantially higher, and the vendors who showed up there were the ones with actual deployed installations, not just demo environments. The conference materials are available through the IIA member portal if you need the full session recordings and whitepapers referenced during the discussions.
