Zaroz
Zaroz Cloud v2 concepts

Organization standing and trust

Zaroz lets a new organization start immediately and widens what it may spend as it builds a payment history. This is the organization's standing. It is per organization and per currency.

What it measures

FigureMeaning
balance_centsthe organization's prepaid balance
reserved_centsheld for purchases and for the worst case of running services
floor_cents, required_centsthe minimum balance a new purchase needs on top of what is reserved
available_centsbalance - required: what a purchase may use
credit_limit_centshow far the organization may owe on invoice (postpaid), 0 for prepaid organizations
open_receivable_centswhat it currently owes
restrictedwhether new spend is refused

Trust is graduated into named tiers, and staff can override a tier. Behavioural signals can restrict new spend and lower the ceiling automatically. A restriction only ever stops new spend: purchases, upsizing, new units. It does not stop services that are already running.

Who sees what

Any member can read standing. The organization's owner gets the full breakdown in detail. Every other member gets only a fixed sentence in message, identical for every reason, so that a restriction never leaks the organization's finances. An organization you do not belong to answers 404.

curl

TerminalCode
curl -sS "$ZAROZ_API/organizations/<org uuid>/standing" -H "$AUTH"

TypeScript

TypeScriptCode
const { body: standing } = await call("GET", `/organizations/${ORG}/standing`); if (standing.restricted) console.warn(standing.message, standing.detail);

Python

Code
_, standing = call("GET", f"/organizations/{ORG}/standing") if standing["restricted"]: print(standing["message"], standing.get("detail"))

Where it shows up

  • restricted: true is why a checkout or a unit start is refused; restriction on the quote and checkout responses carries the reason and the number that would clear it.
  • The quote's required_cents and available_cents tell you before you buy whether the purchase will pass.
  • For organizations with a credit limit, the owner's quote and checkout responses carry a postpaid disclosure of what will be invoiced rather than prepaid.

Debt has a defined ladder, with warnings before every irreversible step: a restricted organization first loses the ability to start new spend, and only after sustained non-payment are services suspended and, much later, data deleted, with notices at 15, 7 and 1 days before deletion. Settling the open receivable lifts the restriction.

The tier names and thresholds are set by Zaroz and can be overridden by staff. Do not hard-code them; read restricted, required_cents and available_cents.

Last modified on