Guide
Program Invitations and Acceptance
Recipient onboarding, email verification, token expiry and versioned terms.
Payouts on the 1st and 15th
Developer, affiliate, and collaborator payouts are available twice monthly, on the 1st and 15th, on the same schedule. Each payout covers eligible earnings from the previous period, plus any older unpaid eligible balance, after a minimum 14-day hold. Earnings still within the hold carry forward to the next eligible payout date. Accepted revenue shares, refund or dispute adjustments, and verified payout details determine the eligible balance. An invitation or calculator estimate alone is not a paid balance or proof of a completed payout. External reseller payments are not funds collected by SoundSync.
Agreement and live participation are separate
Affiliate and collaborator accounting is available for eligible one-time product sales. Live participation requires explicit acceptance by both the developer owner and recipient of the current agreement version and payout policy before future eligible sales accrue shares. Keep payout details verified. An invitation or calculator preview is not collected money, and agreement acceptance is separate from live financial approval. Refunds and disputes reconcile the original shares; recurring-product commissions are not included in this workflow.
SoundSync
Invitation lifecycle
| Stage | Action |
|---|---|
| Proposal | Set recipient email, name, eligible products, rates and effective date |
| Invite | Copy the generated link or request delivery; inspect delivery failure separately |
| Identify | Sign in with the invited email or use the invitation-authorized account setup |
| Verify | Complete email verification; existing two-factor authentication still applies |
| Review | Read developer identity, product names, effective dates and the displayed payout policy |
| Accept | Accept the specific version, terms and payout-policy version |
| Maintain | Revise, pause, resume or end through the permitted management workflow |
A link is a secret
Invitation tokens expire after seven days and are stored as hashes. Used, expired and revoked invitations cannot be accepted. Generating or emailing a replacement revokes older pending links. Do not publish invitation URLs in screenshots, issue reports or public documentation.
Permissions remain separate
Acceptance does not grant developer team membership, reseller authority, product editing or customer-data permissions. Read-only workspace members should review permitted records without seeing management actions. Use Team Accounts when a contributor also needs dashboard access.
Changes require a new decision
Accepted terms are versioned and effective-dated. A proposal does not overwrite current accepted terms. Both the developer owner and recipient must explicitly accept the applicable live terms and payout policy before eligible new sales accrue. Team membership cannot substitute for owner financial authorization.