REGULATION

The licence you find too late

5 min readMonezys

There is a reliable sequence. A team builds something that works. Somewhere near launch, a lawyer or a bank or a payment provider asks a question that nobody had thought to ask, and the answer turns out to determine the architecture. The product then gets rebuilt, or it does not launch.

The question is almost always some version of: whose money is this, while it is in your system?

The activities that are almost always permissioned

  • Holding somebody else's money, even briefly, even in transit, even if you never intended to be a custodian.
  • Holding somebody else's assets, including tokens, on their behalf.
  • Offering a contract whose value depends on a future event — which is what an event contract is, and what a great many products quietly become.
  • Giving advice that a reasonable person would act on financially.
  • Introducing customers to somebody who does any of the above.

None of these is a reason not to build. All of them are reasons to know, in week one, which of them you are doing.

Three legitimate positions

There are three defensible answers, and the wrong one is a fourth: hoping.

  • You hold the permission. Slow and expensive, and sometimes the whole moat.
  • You operate under somebody else's, agreed in writing, with the obligations and the liability written down rather than assumed.
  • You are structured so the activity is genuinely not yours — the money never touches you, the assets are held elsewhere, the contract is between two other parties. This is a design decision, made early, and it is frequently the cheapest of the three.
The rulebook is an input to the design, not a compliance step at the end. Teams that treat it as the latter rebuild; teams that treat it as the former ship something slightly different and keep going.

What this looks like in practice

Half a page, written in week one, answering: what activity are we actually doing, which permission does it need, in which jurisdictions, and which of the three positions are we taking. It is not legal advice and it does not replace a lawyer. Its job is to make sure that when you do speak to a lawyer, the conversation takes twenty minutes and happens before the architecture is set rather than after.

Nothing here is legal advice, and permissions differ substantially between jurisdictions. The point is the timing: ask in week one, not in the week you planned to launch.