fintech_devcon

🎁 Give the #fintech community a gift they’ll actually use: Your hard-earned, hard-won technical wisdom. If you find yourself sneaking away from the holiday chaos for a quiet moment (ideally with a glass of eggnog), it’s the perfect time to submit your talk proposal for #fintechdevcon. Not sure what to share? 🚧 Our attendees want the real stuff. 💡 How you solved a thorny problem in your stack 💡 What broke, how you fixed it, what you'd do differently next time 💡 #Architecture decisions you wrestled with (and tradeoffs you made) 💡 #Developer tooling or workflows you'd recommend 💡 Real lessons from building or debugging #payments, #ledgers, #infra 💡 #Security, #fraud, or #compliance challenges you engineered around If you have multiple ideas, you can submit them all. 👌 🔗 https://lnkd.in/grf6XUAT

In classical accounting, money is treated as perfectly fungible, that is, a dollar is a dollar is a dollar. This is great for describing a company’s financial position. But this assumption holds us back when modern fintechs need to ask more sophisticated questions questions: • Where exactly is this customer’s money stored? • Which transactions involved these specific funds? • Are some treasury holdings riskier than others? When money is treated as identical and interchangeable, it’s impossible to trace its path, context, or risk. In his talk at fintech_devcon 2025, Clément Salaün introduced “the color of money”, a ledgering concept that rethinks how we represent funds, making it possible to answer these questions with precision. #Fintech #DoubleEntry #FintechDevcon https://lnkd.in/duWgSTC2

Daniel Cohen's fintech_devcon talk about Event Sourced Architecture is live 🚀 Most of the applications we use every day (Instagram, TikTok, Amazon, etc.) are read-heavy. A few posts or items are added, then these are viewed by thousands of people. In contrast, payment processing systems like Rainforest are extremely write-heavy. The majority of requests served by our systems involve writing new records. This makes scaling difficult. Event Sourcing is a strategy where every change to the data is written down first, and then applied later. Imagine writing a To-Do list, and then subsequently working it in order. There are some downsides, like having to think about, and write down, all the steps to accomplish a project first. However, it makes it much easier to delegate tasks to other people, or save some less time-critical steps for later. This is the strategy behind an Event Sourced architecture, which Rainforest leverages extensively to seamlessly process billions of dollars in payments each year. 📺 Watch Daniel's presentation: https://lnkd.in/gUKZMssq If this is your jam, and you're an Atlanta-based Software Engineer or Product Owner, check out or open roles! Software Engineer 👉 https://lnkd.in/gSeKpcns Technical Product Owner (Experience Team) 👉 https://lnkd.in/g8e9rs-j Technical Product Owner (Rails Team) 👉 https://lnkd.in/g9r5Zxxr

Clément Salaün’s fintech_devcon talk is out! The color of money: 'Rethinking fungibility in digital ledgers'. Highly recommend if you care about how modern ledgers really work. >> You can watch it on fintechdevcon.io/videos (search for Clem)

Maria Palma from Freestyle Capital and our very own Tyllen Bicakcic dug into the future of agentic payments at fintech_devcon 2025. They discussed what it takes to make AI-driven money movement compliant, secure, and scalable. Here’s what stood out: - Today’s rails still treat every bot like a threat - Agents don’t need bank accounts—they need guardrails, revocable access - Paygent sits at the center of a multi-agent future. The trusted payments agent we built to understand financial intent, enforce policy, and move money safely. 🎥 Click the link to watch the full video: https://lnkd.in/e8R5trvZ

My talk from fintech_devcon 2025 is now live on YouTube 🎥 It’s called “Securing a Banking System’s UI and API” - a deep dive into how to design safer, more auditable fintech systems from the ground up. In it, I cover things like: • Masking and handling database IDs securely • Building APIs that protect users and developers • UI design decisions that reduce security risk • Avoiding the most common (and costly) mistakes in foundational system design The talk is aimed at engineers and product folks who care about the invisible layers of trust that make modern financial systems work. 👉 Watch here: https://lnkd.in/eyJnjurJ Huge thanks to the team at fintech_devcon for hosting such a great event in Denver this year - the range of talks and hallway coffee chats made it one of the most valuable conferences I’ve attended. (If you’re in fintech, bored of your current work task, or just curious about how security, design, and product thinking intersect - this one’s for you.)

We lost $200,000+ on Fintech Devcon this year. Best investment I ever made. When you're building a developer-first payments platform, you face a choice. Drop that same $200,000 at a mega conference and hope someone notices your booth among thousands. Or create something different. Guess which one we chose? Picture this: Harsh Sinha from Wise, running a $14 billion company, standing on our stage. Telling a room full of engineers how he learned to treat his developers better through conversations with me and my team. The head of payments from PayPal sharing war stories about real practitioners solving real problems. Pure knowledge transfer between people who actually built the greatest FinTech companies on the planet. The math might look scary on paper. Speaker costs. Venue. Production. But then there's the X factor. When industry leaders fly in to speak at your event, they're validating your vision. When they reference your platform in their talks, it's worth 20x any billboard. Every founder faces this choice. Spread thin across massive events or go deep with your exact audience. We learned that losing money the right way beats spending it the wrong way every time. To clarify I don't consider this a loss. I think it's the best marketing dollars we could ever spend.

After all the code, the coffee, and the lively debates—one thing’s clear from this year's vintage of fintech_devcon: Fintech builders are ahead of the curve. There's basically no real-estate in your product that's not in scope to be completely revolutionized by AI. None. Zero. Zilch. It's all up for grabs, and the folks in Denver earlier this week? They're all over it. Here are a few recaps of sessions that blew me away on the final day: → The anatomy of agentic commerce. Jeff Pomeroy at PayPal isn't bullish on AI agents reshaping commerce; he's all‑in. Hearing someone of Jeff's pedigree—at a company like PayPal, no less—be so bullish, you can't help but get more excited yourself. We got a blueprint on how to construct the tools, the infrastructure, the APIs—the very scaffolding of an autonomous payments future. → Making REST APIs AI‑usable. Johnny Mejias of Payabli taught us that agents don’t see APIs the way we do. He laid out how to upgrade your API for AI‑readability: clear schemas, documentation that reads like plain English, and a structure that lets agents discover, interpret, and act—so your system doesn’t just work, it delivers. → Building identity foundations for an agentic future – Anvi Banga from Descope walked us through why identity for AI agents isn’t a checkbox; it’s foundational. Non‑human identities, OAuth flows, scoped consent, tool access control wrapped in security, transparency, and interoperability—all pre‑built by design, not bolted on later. I came to Denver to figure out what Quiltt should be doing with AI. I left realizing the better question is: What happens if we don’t? This week made it crystal clear—AI isn’t a sidecar bolted on to fintech. It could be the chassis. To the builders I met this week: keep shipping the future.