Trust
Settlement
Invoices, payment confirmation by operations, and sandbox agreements that never involve money.
Settlement is how an agreement gets paid before its allocation activates. Today there are two methods, and the route decides which one applies.
| Method | Used for | Money moves |
|---|---|---|
| External invoice, confirmed by Cairva operations | Live routes | Yes, outside Cairva |
| Sandbox, no charge | Sandbox routes | No |
Prices are in USD. A quote can't use the other method: a live lot quoted as no-charge, or a sandbox lot quoted for money, is rejected.
External invoice
- The supplier countersigns. Cairva issues an invoice (
INV-…) for the agreement price, and the agreement moves toawaiting_payment. - The buyer pays the invoice outside Cairva and records the payment reference in the workspace. The invoice moves to
pending_confirmation. - Cairva operations check the payment and either confirm it with an evidence note, or reject it with a note saying why. A rejected payment puts the invoice back to
issuedand the buyer sees the note. - Once confirmed, the invoice is
paid, the agreement moves toprovisioning, and activation checks run.
The allocation can't activate until the invoice is paid.
Sandbox, no charge
When the supplier countersigns a sandbox agreement, Cairva records a zero-amount settlement, marked paid, with the note "Sandbox agreement. No money moves." The agreement goes straight to activation checks.
Price
The agreement price is fixed at acceptance: input tokens times the input price per million, plus output tokens times the output price per million. Overage is always a hard stop: the price doesn't grow with usage, and requests stop when the allowance runs out.
Cancellation and voided invoices
If an agreement is cancelled before activation, any invoice that's still issued or awaiting confirmation is voided. After activation, cancellation follows the terms written into the quote. See Agreements.