Refunds + commissions on Finance
Record a refund against any recorded payment (per-row action; the ledger records the reversal — amounts stay L-MONEY strings, idempotency-guarded server-side) and see commission records as jobs complete, with the rule definitions behind them.
If you are building a front end
Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: POST /api/v1/fin/refunds, GET /api/v1/fin/commissions, GET /api/v1/fin/commissions/rules.
Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.
- How to turn it on
- Part of the 'finance' module.
- Who can use it
- RBAC: fin.payments.write (refund) / fin.commissions.read (commissions).
- The API behind it
POST /api/v1/fin/refunds, GET /api/v1/fin/commissions, GET /api/v1/fin/commissions/rules- Where it lives
- /finance
See it in context
Quoting, invoicing & payments — the full walkthrough, step by step: Estimate → quote → invoice → money in YOUR Stripe. We never hold your funds.
Machine-readable
This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.