Guide
Developer Payout Destinations, Fees and Status
Twice-monthly eligibility, Stripe Connect local-bank routes, PayPal setup, provider costs and payout reconciliation.
When eligible earnings are paid
Developers, affiliates and collaborators share the 1st and 15th payout schedule for eligible previous-period earnings and older unpaid balances after a minimum 14-day hold. These are payment-initiation dates, not guaranteed arrival dates. Recorded earnings still in the hold carry forward to an eligible run; unresolved adjustments and destination checks can affect the amount.
Product pricing, checkout charges and SoundSync accounting remain in USD. Eligible Stripe Connect destinations can receive local-currency bank settlement using the available quote. Local bank settlement does not enable multi-currency checkout. PayPal developer payout setup uses USD and remains subject to country eligibility and provider approval.
SoundSync
Choose and verify a payout destination
-
Complete the business profile
Use the actual registered-business country. A bank or PayPal account country is a separate fact; do not change business country to bypass provider requirements.
-
Have the owner select the provider
One payout provider is active per developer and environment. The workspace owner controls destination setup; read-only billing access does not grant onboarding authority.
-
Complete Stripe requirements
Finish the Connect requirements and inspect live readiness. Eligible same-country routes can quote local bank settlement; availability depends on the country, bank and saved account status.
-
Verify PayPal separately if chosen
Use the payout email you own, which can differ from the login email. Verify the eight-digit code, supply the registered PayPal country and confirm the account can receive USD. Live PayPal sending awaits provider approval.
-
Review changes before the run
A destination change can impose a 24-hour wait. A transfer or bank payment in progress can prevent switching providers. Saving an email is not a payment or proof of provider eligibility.
SoundSync
Verify the destination before saving it
The current setup form keeps email verification, account country and destination selection distinct. This is example setup, not a payment; live PayPal sending awaits provider approval.
Sale earnings and the received payout are different
SoundSync covers ordinary payment processing on SoundSync-managed checkout, not on payments collected by outside resellers or partners. Sending a developer payout is a separate service: applicable provider payout, active-account, cross-border and currency-conversion costs are developer-paid and itemized or reconciled against the payout balance. They are not another marketplace percentage or a second checkout-processing charge.
A $49 pre-tax sale less the 10% SoundSync fee produces $44.10 in sale earnings before any agreed affiliate/collaborator allocation. The payout preview then shows applicable sending costs, invoice offsets and other recorded adjustments to the eligible balance.
Where local-currency settlement is available, the displayed FX quote already includes its conversion cost; it must not be counted twice. Cross-border amounts can be estimates. Provider-reported fees are authoritative, and a later difference can debit or credit a future payout. Cent rounding remains in your balance, not a hidden fee.
SoundSync
Read the payment stage, not just the total
| Stage | What it establishes |
|---|---|
| Next-run estimate | Can include recorded earnings that will complete the hold by that run. It is not a completed payout. |
| Approved or submitted | The amount is scheduled or submitted to a provider; it has not necessarily reached a bank. |
| Stripe transfer | Funds reached the connected account. The bank-payout step and bank status are separate. |
| PayPal pending or unclaimed | Not a successful received payment. Live sending still depends on provider approval. |
| Fee reconciliation | Provider-reported fees can settle an earlier estimate and appear as a later debit or credit. |
| History and CSV | Use amount, destination, provider references, fee/FX details and status to reconcile a statement. |
Verification-code limits
A PayPal payout-email code expires after 15 minutes. Wait at least one minute to resend; five sends per hour are allowed. Five incorrect attempts lock that code. Request a new code rather than repeatedly guessing. Verification does not select the payout method; save the destination after verification.
SoundSync
Statements and setup
SoundSync
Payout setup response states
| Response or input | Next step |
|---|---|
| verification.status: pending | The code has been sent, not verified. Enter the current code for the same email and environment. |
| verification.status: verified | Verification succeeded. Saving the payout destination is still a separate action. |
| verification: null | The send result no longer matches an active request, for example after switching providers during delivery. Reload the saved destination and verification state. Do not treat this as verified or silently send another code. |
| Expired, locked or delivery_failed | Use the returned error or current verification state. Respect the cooldown and hourly limits before requesting a new code. |
| confirmPayPalAccount: true | Required when selecting PayPal. Confirm ownership and ability to receive USD; use the actual registered PayPal country. |
| paypalEmail / email | paypalEmail is preferred; email is an accepted alias. If both are omitted, an existing saved PayPal email may be reused. A different email still needs verification. |