1. Payment-provider boundary
Unprice owns the customer money path: plan versions, entitlements, usage, budgets, wallet credits, ledger captures, and invoice evidence. The payment provider still captures payment. Stripe is the built-in production adapter today, and Sandbox is available for testing. The billing boundary is provider-interface based, so a team running its own deployment can add another provider adapter without rewriting the product request path or moving pricing logic back into application code.2. Invoice evidence
Invoice lines should be explainable from the same path that allowed, denied, consumed, reserved, or captured usage. Evidence can include:- plan version
- billing period
- pricing rule
- rated usage events when present
- wallet movement
- ledger captures
- ingestion status and replay state
3. Billing cycles and credits
Unprice supports recurring billing periods and wallet credits. Keep these concepts separate:- Entitlement grants define what a customer can access or consume.
- Wallet credits fund customer spend.
- Ledger captures record reserved or consumed wallet funds.
- Invoice evidence explains how usage and credits became a billed line.