Stripe Connect

Overview

Stripe Connect links your Stripe account to Eclipse for payment and payout visibility. Billing subscriptions for Eclipse itself use a separate Stripe flow.

Setup

1. Open the integrations hub and connect Stripe, or use Settings → Billing when prompted.
2. Complete Stripe Connect onboarding in the Stripe-hosted flow.
3. Return to Eclipse and confirm charges and payouts are enabled.

Notes

• Webhooks are delivered to /api/webhooks/stripe.
• Stripe Connect is the only supported user-visible Stripe connection. Eclipse does not accept Stripe secret keys for direct sync.
• Payout lists always use the Stripe Connect account stored for your active workspace; callers cannot choose another Stripe account.
• Payout decomposition also uses only that workspace’s enabled Stripe Connect account. Eclipse does not read a workspace Stripe secret key or fall back to the Eclipse platform account. The payout summary, complete breakdown, linked orders, replay identity, and audit evidence save together; an incomplete save is retried rather than shown as reconciled.
• Viewing payouts requires integration access. Reconciling a payout requires banking reconciliation access and processes every available Stripe balance-transaction page up to the synchronous safety limit.
• Stripe revenue cards require report access and use only aggregate rows for your active workspace. They do not return raw transaction samples or internal diagnostics.
• Paid-invoice order import reads every supported Stripe invoice line before it writes locally. Eclipse then saves the order, all line items, processing-fee evidence, and audit record together; incomplete imports are rejected, safe retries reuse the original order, and the order workflow owns ledger posting.
• Direct batch import of invoices created in the Stripe Dashboard is unavailable. Create customer invoices in Eclipse; use paid-invoice order import only for historical Stripe product sales.
• Stripe webhooks do not automatically turn provider-created Dashboard invoices into Eclipse invoices. Already-linked Eclipse invoices can receive provider status and balance updates, but webhook payloads never replace Eclipse invoice line items. Repeated payment events reuse the original pending payment evidence; historical paid product sales use the reviewed order import.
• Stripe PaymentIntent events do not create or update vendor payouts, and generic charge-refund events do not rewrite imported orders. Record vendor payments from bills or approved payment runs. Linked-invoice refunds use the reviewed refund workflow; refund reversal for historical paid-sale imports remains unavailable until its order, ledger, fee, tax, COGS, and inventory effects can commit together.
• Eclipse does not change invoice accounting while a Stripe refund is pending or failed. After Stripe marks an invoice refund succeeded, Eclipse applies it to the original workspace payment: an unposted receipt is reduced or canceled, while a posted receipt receives a partial or full reversing entry. If the accounting commit cannot finish, Eclipse leaves critical review work and retries instead of reporting the refund as posted.