Build with SoundSync
Build with SoundSync
Build with HISEScript, native HISE, JUCE, or custom HTTP, and connect storefronts and approved partner fulfillment.
SoundSync
Checkout and commercial details
| Question | Current support |
|---|---|
| PayPal accepted at checkout? | Yes. PayPal is accepted for one-time purchases. Subscription checkout uses Stripe. |
| Stripe checkout? | Yes. Stripe supports card payments and available wallets; choices depend on the customer and checkout configuration. |
| Supported currencies? | USD only currently. Prices and checkout charges are presented in US dollars. |
| Developer payout schedule? | Developer, affiliate, and collaborator payouts share the 1st and 15th schedule for eligible prior-period earnings after a minimum 14-day hold. Developer payouts use Stripe Connect. |
| Native affiliate programs? | Yes. Product-specific referral attribution and accepted commission agreements, with eligible earnings on the shared 1st and 15th payout schedule after a minimum 14-day hold. |
| Collaborator revenue sharing? | Yes. Allocate agreed product revenue shares to contributors without granting customer-table access. Eligible earnings use the same twice-monthly payout schedule and minimum 14-day hold. |
| Reseller integrations? | Yes. Approved relationships, assigned products, external orders, serial fulfillment, and partner APIs. |
| Product migration supported? | Yes. Migrate your product catalog using public store/product pages or CSV, TSV, XLSX, and JSON exports. Review supported media and delivery files before publishing. |
| Pay-what-you-want pricing? | No. SoundSync does not support pay-what-you-want pricing. Paid checkout offers start at $9.99 after discounts, before tax. |
SoundSync
Choose by build environment
| Path | Use it when | Integration responsibility |
|---|---|---|
| HISEScript | You want licensing without modifying HISE source | Include the generated script runtime; test script-level enforcement in your project |
| HISE C++ | You can rebuild HISE and the exported plugin | Install native sources, patch and rebuild HISE, then patch and build the export |
| JUCE 0.7.3 | Your plugin or application uses JUCE | Own licensing in the processor; attach the editor UI and guard every audio callback |
| Custom HTTP | You maintain your own runtime and activation interface | Implement transport, ownership, device identity, storage, revalidation, and access decisions |
| Storefront embed | You already have a website | Install the full commerce package or select a standalone content embed |
| Partner API / WooCommerce | An approved reseller sells your products externally | Agree product scope, delivery model, mappings, credentials, and refund handling |
Licensing and storefronts solve different jobs
Licensing determines whether a customer and device can use a product. Store and My Products provide browsing and owned-product access. A hosted or embedded website is not the same thing as a plugin licensing package.
A Test Connection result confirms product credential connectivity, not customer ownership, activation, audio unlock, or completed checkout.
Offline support depends on the package
JUCE 0.7.3 supports signed offline access for the grace period selected in product Access settings, through 90 days. A prior successful activation or validation and the matching package verification keys are required. Startup uses a verified unexpired grant or online authorization. Zero, disabled, missing or expired grace requires online authorization; confirmed denial or deactivation locks access. Regenerate and rebuild older plugins to use this release.
HISEScript can use configurable offline grace after a prior valid state. Confirmed invalid or revoked access must not become offline-valid. Native HISE and custom clients must follow their own generated contract rather than inherit a promise from another package.
SoundSync
Start with the matching guide
SoundSync
Beyond plugin activation
SoundSync
Affiliates, collaborators, and team members
Affiliate programs
Agreements, referrals, attribution, and earnings.
Collaborator sharing
Product-specific contribution agreements.
Recipient payout policy
Funded shares, consent, eligible balances, and adjustments.
Team Accounts
Dashboard access is a separate permission.
SoundSync
Bring your catalog and shape your storefront
Plan what moves with your catalog
Product migration is supported for catalog information and supported files. Customer accounts, historical orders/payments, active subscription billing authority, and marketing consent need separate transition arrangements; they are not automatically copied with the catalog. Read the product migration guide for the supported workflow.
Working with partners and contributors
Integrate licensing without sharing your dashboard account. Affiliate and collaborator participants have separate agreements and accounting; payouts follow the 1st and 15th schedule after the minimum 14-day hold.
SoundSync
Agreement and payout details
Program payouts
Eligible earnings, original-share refunds, and recipient readiness.
Protect your account with two-factor authentication
Add an authenticator to your SoundSync account and keep single-use recovery codes in a private place. Enabled accounts complete a two-factor challenge at sign-in. Team members use their own accounts and product-scoped permissions rather than sharing the owner login.
SoundSync
Account protection and recovery
Account Security
Enrollment, recovery codes, replacing an authenticator, and getting help.