Recurring payments publish your revenue

Every subscription business runs on one number. Monthly recurring revenue is what you report to investors, what you use to plan hiring, and what an acquirer values you on. On a public chain, you do not report that number. You publish it continuously as it changes.

A subscription is not one payment. It is the same amount, from the same counterparty, at a fixed interval, repeated until someone stops.

That is the most legible shape a payment can have.

A pattern is easier to read than a payment

A single transfer is a fact: someone paid someone something. On its own, it is not worth much.

A payment that repeats every month is a relationship. Repetition tells an observer which transfers belong together, which addresses are customers rather than one-off counterparties, and how long each of those relationships has lasted. No labels are required. The cadence does the labelling.

This is the uncomfortable part. What makes recurring revenue valuable to you is its predictability, and predictability is exactly what makes it readable to everyone else.

What someone can compute without asking you

Count the recurring inflows and you have the customer count. Add them up and you have monthly revenue. Watch them over a few periods and you have the growth rate.

The subtractions are worse than the additions. A subscription that stops is churn, and it is visible in the month it happens rather than in the quarter you choose to disclose it. A large one that stops is a lost account with a date attached. A competitor, an acquirer in the middle of a negotiation, or a journalist can read it at the same time you do.

The amounts expose the price book on top of that. Cluster recurring payments by size and the tiers fall out, including the discounts you gave to win specific accounts.

The leak runs in both directions

What a company pays for every month is a fair description of how it operates.

If you sell to businesses, every customer who pays you on a public chain is also publishing part of their own vendor list. Their stack, their spend, and the fact that they switched to you last March are all readable. Confidentiality is not only something you want for yourself. It is something your customers trust you not to expose on their behalf.

The leak is in settlement, not in billing

These two get confused, and the difference decides where a fix has to sit.

Billing decides who owes what and when: the schedule, the retry, the proration, the dunning email. Settlement is where the money actually moves. Your billing system can be entirely private and the leak still happens, because the leak is in the settlement, and on a public chain settlement is a broadcast.

So encrypting the database does nothing. The transfer it produces is the part that is published.

What confidential settlement changes

In Sova's confidential mode, balances, amounts, and counterparties are encrypted on-chain with fully homomorphic encryption. A payment can settle without publishing who paid or how much. Apply that to a payment that repeats, and the repetition stops adding up to a revenue figure that anyone can read.

Compliance is not traded away for it. Sanctions screening runs at protocol level, before a transaction reaches the chain, on every plan. A relationship that produces a payment every month is therefore screened every month, not only when it starts.

Selective disclosure covers the cases where the numbers do need to be shown. They can be disclosed to an auditor or regulator when required, without publishing the book to the market.

Sova never holds the funds at any point in this.

The honest limits

Encryption hides the amounts and the parties. It does not hide the fact that something happened. A payment that repeats on a schedule still produces a transaction on that schedule, and cadence is information in its own right. An observer with timing data and enough off-chain context may still infer the shape of a business whose figures they cannot read.

Confidentiality here means confidentiality from the public, not from your customer. Your customers know exactly what they pay you and will continue to know. What changes is that your customer list stops being a public document.

None of this is a billing product. Schedules, retries, upgrades mid-cycle and the rest of subscription logic are a separate problem, and confidential settlement does not solve them. What is described here is what encryption does to a payment that happens to repeat.

Confidentiality also does nothing for retention. A ledger that hides churn does not reduce churn. It only stops your competitors from measuring it sooner than your own board does.

The bottom line

A subscription business is a set of relationships that repeat, and on a public chain, repetition is the signal that makes every one of them legible.

Your investors should hear your numbers from you. Your competitors should not hear them first.