FCA Readiness Doesn't Mean Waiting

Why compliance became a feature, not an afterthought

When we started building the tipping system for MRVL's creator ecosystem, we had two paths. We could ship fast and sort out the regulatory questions later, or we could make every decision with an eye toward what the Financial Conduct Authority would need to see.

We chose the second path. Not because it was easy. Not because it was fashionable. But because we were building something for real creators who earn real money.

Streamr streamers, Foundr makers, and the faith creators who make up a significant part of our audience don't have legal teams. They need a platform they can use without wondering if they're inadvertently breaking rules. That meant integer pence throughout the system, meaning every transaction is tracked to the penny, with zero rounding that creates audit gaps. It meant designing our fee structure so it could survive scrutiny. It meant thinking about AML thresholds not as a nice-to-have, but as a core safeguard built in from the start.

The schema decision that took longer than the code

Here's what most people don't realise about financial software: the database structure often matters more than the interface. We spent weeks on Seedr's payment schema before we wrote a single line of the SDK.

Every transaction, every fee calculation, every payout sits in a Supabase backend designed with the FCA's eventual Phase 3 authorisation in mind. We have a single source of truth for fees. No spreadsheets. No hidden logic. Just functions that anyone could audit. When a creator tips another creator, or a community member sends their first tip, that transaction is recorded in a way that will make sense to a regulator in three years, or five years, or whenever we apply for Payment Institution status.

The minimum payout is £20. The minimum tip is £5. Those aren't arbitrary numbers. They exist because they fit the shape of what regulation requires. And because I've learned that creators prefer clarity to false convenience.

What you can actually launch with today

Here's the thing people miss when they hear "FCA-ready": it doesn't mean you have to wait. Seedr runs on Stripe Connect, which is already FCA-authorised. You can embed a SeedrButton in your Streamr app right now, in three lines of Swift or Kotlin. Your audience can tip without creating an account. Money hits your creator bank account every Monday morning, starting at £20 minimum.

The faith community creators we've onboarded understand this immediately. A pastor running a weekly Streamr stream can set up a profile at seedr.app/@handle, share the link with their congregation, and receive tips for their ministry without friction. A church member can send £5 or £50 without signing up for anything. The compliance layer is invisible because it's already baked in.

That's not theoretical. It's shipped. People are using it. Payouts are happening.

The fee that tells a different story

Most tipping platforms charge 5% and call it a day. We charge 5% standalone, but the fee drops to 1.5% if you're a Foundr Free creator, and 1% if you're Foundr Pro. This isn't a pricing trick. It's built into the schema because we wanted the platform to work better for the creators who commit to their craft within the wider MRVL ecosystem.

A Streamr streamer who also publishes on Foundr shouldn't be penalised by Seedr's fee structure. They should benefit from it. The regulatory trail backs this up too. Every fee tier, every calculation, every payout is logged. No mystery. No excuses when something needs to be explained.

Why this matters in 2025

We're not getting FCA-authorised to brag about it. We're doing it because the regulatory environment for financial platforms is tightening, and because we believe creators deserve infrastructure they can trust. In five years, when MRVL Pay reaches full authorisation, the creators who joined Seedr today won't suddenly find their payments interrupted or their data restructured.

They'll know that the platform was built to last.