Most subscription systems make one critical promise and then quietly break it in practice: “you will be charged the price you agreed to.” In a traditional setup, the price lives in a private database controlled by the merchant or billing vendor. That means the value can be changed unilaterally, retroactively, or accidentally through internal tooling. Even honest teams can introduce drift between checkout, invoicing, and payment execution when multiple services update plan metadata independently.
Recuro treats this as a protocol problem, not a UX problem. The amount, interval, and merchant identity are committed to an on-chain Plan account at creation time. Once the plan is created, the amount cannot be edited in place. There is no “silent update” endpoint, no mutable row, and no admin override hidden behind internal permissions. Billing automation always reads from that same account, so execution and agreement remain cryptographically coupled.
This changes the trust model for subscribers. A subscriber is not granting open-ended permission to a merchant’s backend. They are approving one explicit cycle amount tied to one explicit plan definition. If the merchant wants to charge a different amount, they must publish a new plan and ask users to opt in. That creates a clean migration boundary: old price remains old price, new price is visibly new price, and consent is explicit.
It also benefits merchants who care about long-term retention. Price immutability is a signal of discipline and predictability. If you sell fixed-rate memberships, annual support plans, or loyalty tiers, committing price rules on-chain can increase conversion because customers understand the rules cannot be changed in the dark. The guarantee is enforceable by code, not policy text.
Of course, immutable pricing introduces constraints. It is not a natural fit for fully dynamic metered billing where every cycle depends on variable consumption. In those cases, teams can run a hybrid model: Recuro for the base recurring component and a separate settlement path for usage deltas. But for the majority of recurring products where predictability is the product promise, immutable plan pricing is not just safer. It is operationally cleaner, easier to audit, and easier to explain to users and regulators.
The practical outcome is simple: the price the customer approved is the price the protocol can execute. Nothing else has authority over that number.