Aeionica + Stripe Connect
Aeionica models percentage-based royalty splits per track and pays each collaborator directly — real Stripe Connect destination transfers, with PayPal and manual modes alongside. Every split is computed against a snapshot, recorded in a per-sale payout ledger, and retryable on failure. Aeionica takes 0% of the split — only Stripe's processing fee applies, and it goes to Stripe. Read the "What This Does NOT Do" section before you assume the on-sale trigger is wired end-to-end.
What Connects
`
Split Mechanics — On the Transaction, Not Month-End
`
Setup
Two things have to be in place before a split can pay out:
What This Does NOT Do (Read This)
The split engine — percentage model, ledger, real Connect/PayPal transfers, retry — is built and functional. Three gaps matter for planning, and we'd rather you know them up front than discover them in production:
FAQ
Real. `splitSale()` issues an authenticated `POST` to `api.stripe.com/v1/transfers` as a destination transfer to the collaborator's `acct_…` account, and stores the returned transfer ID on the payout ledger row. If `STRIPE_SECRET_KEY` isn't set, the call throws rather than fabricating a success.
Not today. The transfer code and ledger are real, but the trigger from `commerce.order.paid` into the splitter is not currently wired. Plan around driving payouts through the ledger and retry endpoint until that hand-off ships.
Manually right now — the `acct_…` id is stored on the collaborator record. There is no in-app Connect onboarding / account-link flow yet.
By default 0% (`AEIONICA_PLATFORM_FEE_PERCENT` defaults to 0). Stripe's own processing fee still applies and goes to Stripe. If you set a platform fee, it's deducted from each share before transfer.
Both are supported per collaborator via `payoutMethod`. `paypal` runs a real OAuth + payouts call on the same path (same unwired-trigger caveat). `manual` records the ledger row and leaves the actual payment to an admin.
Through the core Commerce recurring-billing engine (Stripe subscriptions). If the Commerce subscriptions service isn't registered, Aeionica returns null honestly rather than inventing a subscription ID. That revenue is not routed through collaborator Connect transfers.
Splits that go to your artists, not to us.
Percentage-based royalty splits, real Stripe Connect destination transfers, a per-sale payout ledger with retry, and a true 0% platform cut. Bring your own connected accounts today; automatic on-sale payout is on the roadmap.