Why we said no to a tip button everywhere
Two weeks before launch, a developer reached out. Could they embed SeedrButton in their own app, outside MRVL? It was a reasonable ask. The answer was no. Let me explain why that felt right, even though it meant walking away from potential early traction.
The temptation to open the gates
When you build a tool, the first instinct is to make it as useful as widely as possible. An SDK with 3 lines of code is genuinely frictionless. Swift and Kotlin ready. A few developers could have plugged SeedrButton into their own apps, their own communities, their own audiences within weeks. Revenue would have followed. Stripe Connect was already doing the heavy lifting on payment processing.
But Seedr isn't a payments layer. It's part of something bigger. The moment we let the button live outside the MRVL ecosystem, we'd be making a silent claim about what it means. We'd be saying 'this is a generic tipping solution' rather than 'this is how creators inside our ecosystem support each other.' That shift in identity would have felt small at the time. It would have felt like pragmatism. And it would have been exactly the wrong kind of scaling.
Why creators, not just payment rails
Seedr was built for a specific moment: when a faith creator is live on Streamr, or when someone shares a Foundr project, or when a comedian launches on Giggl. The magic isn't the transaction. It's that the person on the receiving end is part of a community that understands tipping as generosity, not subscription tax. The fan who sends 5 Seeds isn't buying a product tier. They're saying 'this moment mattered to me.'
That context only exists inside MRVL right now. A third-party app wouldn't have that. It would have a button, yes. But it wouldn't have the soil where the behaviour grows naturally. We'd be watching Seedr become a feature, not a movement. Creators matter more than ubiquity at this stage of what we're building.
The schema decisions that locked us in
Behind the 3-line simplicity is something more serious: every field in our database is built to be FCA-ready. We're Phase 1 of MRVL Pay, and we're running clean audits against schemas that Stripe Connect handles today but that we will own directly by 2028. Everything is integers in pence. The fee logic is centralised. Weekly Monday payouts aren't random, they're scheduled. The minimum payout of £20 and minimum tip of £5 aren't marketing boundaries, they're regulatory guard rails.
If we'd let SeedrButton run outside MRVL, we'd be running that same compliance logic across systems we don't control. That's where complexity breeds risk. For now, keeping Seedr inside the ecosystem means we can make decisions fast and audit them thoroughly. When we're Payment Institution authorised and we own the actual payment rails, then we can think about expansion. Not before.
What v1 is actually for
Version 1 isn't about being everywhere. It's about being reliable for the people who are already here. We've got Streamr streamers. We've got faith creators and church community members who understand generosity. We've got Foundr makers who talk about monetisation as a milestone, not a hustle. Those are the folks who should be tipping and being tipped inside Seedr first. No account needed, Stripe Connect handling the payment, creator web profile at seedr.app/@handle, analytics in the dashboard, money landing on Monday.
That's complete. That works. That needs no apology. But it only works if we control the experience end to end. The moment the button lives somewhere else, we lose that control. We become infrastructure. We become a feature plugged into someone else's story. We'd rather be the home.
What changes when it matters
This isn't a permanent no. It's a strategic one. By the time we've hit real creator volume, by the time we've proven that Monday payouts are reliable and the analytics make sense and the 5% fee (or lower, if creators are Foundr members) feels fair, we'll have a different conversation. We might open the SDK. We might even encourage it. But we'll do it from a position of knowing what we're protecting, not what we're missing.
Right now, we're still watching behaviour. We're learning what creators actually do with the button. We're seeing which audiences tip most, which moments matter most, whether £5 minimums make sense or whether they should shift. None of that learning happens as clearly if the button is scattered across a hundred apps we can't see into.
When something is young and precious, you don't hand it to everyone immediately. You tend it carefully. You watch it grow in the right conditions first. So here's the question: if you're a creator inside MRVL, what would it take for tipping to feel like a natural part of how your community supports you?
Ready to try Seedr by MRVL?
One tap to download. No sign-up wall.