- Shipped
- lúc 03:07 12 tháng 11, 2026 UTC
- Author
- Kamo
- Commit
- bbbf950
Stripe Connect for every Line of Business: an organization connects its own Stripe account (a Standard account; the personal-loans lender account gets card payments requested instead of a second account), and a customer's card payment page for one of its invoices is a Checkout session created ON that account - a direct charge, no platform fee, the platform's own account never involved. Every Connect request carries its own key (STRIPE_CONNECT_SECRET_KEY from the optional Secret stripe-connect-credentials), never the global platform key; a live key is refused unless STRIPE_CONNECT_ALLOW_LIVE=true, and with no key nothing is offered. - InternalConnectController (X-Internal-Auth): status, onboarding link, refresh, disconnect, email-receipts switch, open a page (one per invoice: an earlier paid page stops a second charge, open ones are expired), sync a page or an invoice's open pages. - POST **************** signature verified against its own secret, read as plain JSON so the API-version mismatch that broke the platform endpoint cannot, claimed in BILLING_STRIPE_WEBHOOK_EVENT as CONNECT:<account> (the platform replay sweep skips that prefix), live events ignored unless allowed. A paid page is recorded once and SecurityService is told to put it on the invoice.