Payments & Partner Settlements · Documentation
Architecture
Payments & Partner Settlements's pipeline, its owned data, the events it emits/consumes, and what is out of scope.
← Payments & Partner SettlementsDeterministic accounting, no metered stage
Captures and settlements are computed deterministically from the shared bookings and partner tier — there is no LLM stage and no cost ($0). Approve and hold are owner-gated state changes that emit events and write an audit row through the shared store. The settlement math (commission by tier, 18% GST, payout) is fixed and reproducible.
Owned data, events + simulated money
The app owns demo_eco_c6_payment_event (capture / refund / chargeback, all simulated) and demo_eco_c6_settlement (gross, commission, tax, payout, booking count, status). It emits settlement.approved and payment.captured (payout). The data invariant holds — owner writes canonical, a viewer's actions are credential-scoped, ephemeral, and reset-clearing (setWhere-guarded). Out of scope and simulated: all payments, payouts, and the payout confirmation comms — there is no real PSP, bank, or SMTP, and that stays true in Stage-2 too. Honesty is inspector-only.