> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unprice.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Billing

> Invoice and payment-provider evidence for the customer money path.

Unprice connects request-path usage decisions to invoices and payment-provider records. It does not
replace your payment provider, tax engine, accounting system, or revenue-recognition suite.

## 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.

## 4. Payment methods

Manage customer payment methods through the payment provider integration. Unprice stores
provider-specific references so your app can connect customer money-path state to the provider that
settles payment.