Campus Payments

Campus Payments moves and authorizes value while keeping identity, application authority, and exact financial intent separate.

Exact intent

Ordinary application data uses the authenticated Campus session. Fresh passkey assertions are reserved for financial intent, Wallet recovery and backup, and comparable authority changes.

The Wallet architecture separates browser-held recovery protection, public wallet state, and threshold signing. Seller applications own products and merchant request signing, but never create, restore, duplicate, or store the user’s payout Wallet.

Economic composition

Applications can participate as software products, paid services, or paid MCP tools. Payment proves the exact purchase or admitted request; it does not grant unrelated permissions or bypass model, resource, or audience policy.

Continue with Permissions, MCP, Campus app packages, and the repository’s private payments model for implementation work.