Understanding funding, usage, earnings and settlement
Follow quotes, reservations, usage, receipts and settlement without conflating them.
On this page
Understand the financial lifecycle of authorized business work. The planned outcome connects quote, funding, reservation, consumption, receipts and settlement without inventing a separate application wallet.
Keep the owner clear
The account owns funds and application attribution. Workspace visibility and delegated payer authority are distinct. Operator earnings and affiliate commissions are not the same pool as customer prepaid credits.
Account/application cash-spend and prepaid-usage limits are four independent optional settings, each defaulting to none.
Follow the money and work
A quote describes versioned scope and price. A purchase needs verified settlement before prepaid funds are credited. Reservation, consumption, release, refund and correction have distinct meanings and authority.
Saved Catalog quotes never expire. Funding a shortfall does not authorize broader work or new prerequisites. Auto-topup needs explicit consent; a stored card is insufficient.
Read receipts, not assumptions
A payment redirect is not proof of settlement. Submitted physical proof is not accepted proof. Accepted proof, earning accrual and completed payout remain separate events.
For example, an operation can finish partially while unused reservation is still awaiting its authoritative release outcome.
Availability
Business finance APIs are planned. New developer keys cannot spend. Customer statements and requests can be public within scope; financial reconciliation, pricing administration, provider payout controls and manual corrections remain privileged.