- Ya
- 7 Agosti 2026, 02:11 UTC
- Mwandishi
- kamo
- Ahadi ya
- 96a48c7
Member tab (self-only, team members only): balance + ledger, commissioned opportunities, payout setup, and withdrawals. Account settings gains Organization Stripe and Commission Processor. The member tab is gated on isSelf and the member TYPE, never on a right. checkRight returns true for everything under active god mode, and the page's canViewOtherMemberAccount ORs in unrelated rights including **************** — so a right-based gate here would show one member's balance and bank details to anyone holding any of them. 'My Payouts', not 'My Bank'. Members almost never have a Stripe account and cannot attach one if they do: OAuth read_write refuses accounts controlled by another platform. Their employer's platform creates a payout-only recipient account and they verify their identity. The panel states what Stripe collects, that Stripe has no support relationship with them, and that money takes roughly 6-8 calendar days to arrive - none of which they should have to discover afterwards. Organization Stripe is a guided checklist, not a form, because Stripe has no API for becoming a Connect platform. Step 6 carries a full warning rather than a hint: an org whose Stripe balance pays out automatically loses the commission float before the release job runs, and every transfer then fails for insufficient funds with no Stripe event to explain it. Money is a decimal STRING end to end and is never Number()-ed except to choose a colour. Negative amounts are real - a voided commission becomes a draw - and the codebase had no convention for showing one, so they render in the error tone with an explicit minus and a Draw chip. Sub-tabs sync to ?sub=; SettingsView owns ?tab= and rewrites it on every tab change. The BFF route exists because CommissionService is ClusterIP-only - without it the whole feature 404s while every service is healthy and every build is green.