Different people, different perspectives, one Ypsilon
We're going to use this blog in a unique way. Rather than filling it only with polished company announcements, we're going to hand it over to the people who are actually building Ypsilon.
A different voice each week
Every week, someone from the team will write a post. There's no fixed format. An engineer might write about a problem they've been working through. Someone in operations might describe what happens when a digital system meets the very physical world of cash and live venues. Our compliance team might explain a regulatory change in plain language. Someone in product might explain why a small feature took twenty conversations to get right. And now and then, someone will simply share a view on where payments are going.
The aim is to give readers a sense of how the people behind Ypsilon think, which a corporate news feed rarely does.
Why we're doing it now
Payments are going through an interesting period. The lines between payments, wallets, banking infrastructure, identity, loyalty and embedded finance keep shifting. Instant payments have changed what people expect in terms of speed, new technology is changing how value can be represented or transferred and regulation is developing alongside all of it. Businesses are also asking how much control they ought to have over their own financial infrastructure. There's plenty to write about and we think it's more useful to look at it from several angles, not just one.
We won't always agree
Our team includes people from technology, payments, compliance, operations, business development, design and entrepreneurship. When they get together there's debate, sketching and usually more than one version of the same diagram before something better comes out of it. We'd like the blog to reflect some of that.
More than press releases
We'll still post important company news here. But we also want to cover the bigger questions behind what we do. Why should a business have more control over how value moves through its ecosystem? What does "instant" actually mean in practice? Where should compliance sit when you're designing financial technology? And which parts of today's payment infrastructure are genuinely necessary, and which are just habit?
The first post from the team goes up next week.
Comments