Why we publish who we don't serve.

Most fintech companies treat their restricted-activity list like a state secret. They’ll tell you in a discovery call. They’ll tell you in week three of onboarding. They’ll tell you at the bottom of page 14 of a PDF they email after you sign the NDA. The one place they won’t tell you is the front page of their website.

We took the other route. Three weeks ago we published Who we don’t serve — a plain-English list of every sector and country our regulated providers can’t move money for. Not because we love the lists. Because the list was already true, the list already governed every “yes” we said, and the only difference between publishing it and not publishing it was whether the wrong-fit prospect found out in two minutes or two months.

The compliance posture is the product

Here’s the thing about a reseller business in regulated finance. The actual product — the e-money licence, the FCA registration, the safeguarding bank — sits with your provider. What you own is the relationship and the policy. If you treat the policy as something to hide, you’re saying the same thing every other reseller says, which is: “trusted network”, “global coverage”, “compliant infrastructure”. None of those phrases are wrong. None of them are different from anyone else’s, either.

Publishing the actual list of exclusions is the only move that’s hard to copy. A competitor can spin up the same provider stack in six weeks. They can hire the same team. They can’t bring themselves to put “we don’t onboard CBD, fortune-tellers, or speculative FX traders” on the homepage — because that requires accepting that you’d rather lose ten enquiries from the wrong businesses than keep them politely guessing.

What the list does, operationally

Three things, in this order:

• Self-filter. Two-thirds of the prospects who’d have wasted onboarding cycles never make the enquiry. The form fills with cleaner leads. The 20-minute call is shorter.
• Pre-empt the trust question. The board-level question on every crypto product right now is “are you actually regulated, or are you sliding it past us with vocabulary”. The list is the answer. It’s the operational expression of “regulated by design”.
• Force our own discipline. The list lives on the public site. If a provider changes its policy and we don’t update within a week, the lie is visible. That keeps us honest in the back office in a way that an internal Notion page never would.

What the list isn’t

It isn’t a marketing manoeuvre. It isn’t there to make us look brave. It isn’t a way to opt out of compliance — every name on the list is on it because a regulated provider in our network won’t process it, full stop. We’re not adding sectors for taste. We’re surfacing what was always true.

It also isn’t permanent. Lists change. Provider risk appetites shift. We commit to one thing: when something changes, the page changes within a week. That’s the bar.

Where this goes next

The lists are step one. Step two — already in the pipe — is publishing the policies behind the lists in the same plain-English voice: what makes a crypto business “clean” enough for our regulated provider to onboard, what the enhanced-due-diligence path looks like for the soft-no sectors, where the corridors thin out and why. The thesis is the same: anything we already know is true, and anything our partners already publish, should be discoverable in two minutes on the site.

If we get that right, the next reseller in this category will have to make a choice. Match us — and accept the same operational discipline. Or hide the policies in a PDF, and explain to their compliance reviewer why theirs is the second-most-transparent option.