Why we built Seedr on Stripe Connect, not something custom
On a Monday morning in September, a Streamr creator named Marcus messaged us. He'd just received his first tip from a viewer in Lagos. His first question wasn't about the amount. It was: 'Is this actually safe?' That one question shaped everything about how we built Seedr.
The problem with building payment rails from scratch
When we set out to build a tipping platform for MRVL creators, we knew we had two paths. We could licence payment infrastructure and build a full Payment Institution from day one. Or we could choose a partner that was already FCA-authorised, give creators a real product to use now, and keep our roadmap honest about when we'd move to phase two.
The first path sounded impressive in a pitch deck. The second path meant we could actually ship something useful this year, not three years from now waiting for regulatory approval.
Stripe Connect solved a specific problem: it's already FCA-authorised. Creators like Marcus could receive real payouts through a system with decades of payment infrastructure behind it. No corner cutting. No 'we'll upgrade the security later.' We took the FCA-ready architecture seriously from day one. Every number in Seedr flows through integer pence, not floating point. Every fee is versioned in a single source of truth. Every transaction above £10,000 gets flagged for manual review. These aren't nice-to-haves we'll add when we scale. They're how we built it.
What Stripe Connect actually gave us (and what it didn't)
Stripe Connect's beauty is that it handles the hard parts. Bank account verification. KYC checks. The routing logic that makes sure a creator in Manchester can receive money from a supporter in São Paulo without either party thinking about currency or compliance. That's not glamorous work, but it's the stuff that breaks startups who try to DIY it.
What it didn't give us was the layer above it. We still had to design how creators set up their profile at seedr.app/@handle, how they see their weekly payouts every Monday, how fans can tip with no account in three lines of Swift or Kotlin. Stripe Connect was the plumbing. We built the product around it.
That separation felt right. We weren't trying to reinvent payment settlement. We were trying to make tipping feel natural inside the apps creators and their audiences already use.
The creator fee question
Early on, we had to decide on fees. We settled on 5% for standalone creators, then offered 1.5% for anyone on Foundr Free and 1% for Foundr Pro members. The logic was simple: we wanted to reward creators who were already building with MRVL's other tools. But we also had to be honest about what we were actually doing.
Every fee decision is live in our codebase where anyone can audit it. Not hidden. Not changed per user. When we launch creator analytics or a branded profile option (Creator Pro at £4.99 a month), those are upgrades, not tricks. The baseline tipping stays the same.
That fee structure matters for our roadmap. It tells us when we can move to phase two and eventually phase three, where MRVL Pay becomes our own Payment Institution. Right now, Stripe's fees plus our platform fee make the maths work. Later, when we've scaled to millions of tips, we can absorb more of that cost and keep creators' take-home higher.
Why this matters for faith creators (and everyone else)
Our beachhead audience has been faith creators and church communities. They're not trying to build a SaaS company. They're trying to do meaningful work and get supported by people who believe in it. A pastor running a Streamr channel shouldn't have to understand payment settlement or regulatory status. They should tip a button, set up their profile, and get paid every Monday.
Stripe Connect gave us that. It let us focus on the experience, not on becoming a bank. And it let us stay complicit with the FCA ahead of time, not scrambling to retrofit compliance later.
That's not a compromise we're making in phase one. It's a choice that keeps us honest about what we're good at and what other companies are better at.
What phase two and three actually mean
Here's the thing about being transparent about your roadmap: people ask follow-up questions. 'When do you become your own Payment Institution?' 'What changes when you go FCA-authorised?' 'Will our fees go down?'
The honest answer is 2028 for full authorisation, but that's not the whole story. Phase two isn't just 'more of the same with our own licence.' It's when we can start offering features Stripe's general-purpose API doesn't let us build. Instant payouts if a creator wants them. More granular analytics. Multi-currency support that actually works for our global creator base. Those aren't pie-in-the-sky features. They're all technical paths we've sketched out. We're just not forcing them into phase one when Stripe Connect does the job better.
Phase three is when MRVL Pay becomes truly ours. But that doesn't happen at the expense of phase one working brilliantly for creators and their audiences right now.
When Marcus got his first payout the following Monday, he didn't care about our infrastructure choices. He just knew the money was real and it arrived when he expected it. That's the only measure of Stripe Connect that matters: does it let creators focus on what they do best? For us, the answer was yes. The question is whether it stays that way as we grow.
Ready to try Seedr by MRVL?
One tap to download. No sign-up wall.