Sandbox Billing

Sandbox usage is budgeted and recorded with receipts. The billing surface shows how much work was reserved, captured, finalized, or invoiced.

Budgets

Each sandbox launch can set a maximum spend. OpenPond uses that budget to reserve usage, enforce runtime limits, and stop work when the limit is reached.

Receipts

Receipts record the lifecycle of sandbox spend:

• reservation
• usage ticks
• capture
• finalization
• release after failed or zero-spend work

Use receipts to verify what ran, when it ran, and how much budget was consumed.

Payment rails

Organizations may use different settlement modes depending on configuration:

• Stripe credit balance
• stablecoin MPP session settlement
• manual invoice
• internal managed tracking

The sandbox billing UI separates normal organization billing from internal admin invoice and payment tools.

Invoices and credits

Account credits can fund sandbox usage. Manual invoices can include sandbox compute pass-through along with consulting, setup, template, or support line items.

See Operating Wallet Funding for wallet funding basics.