Skip to content
SoundSyncAudio software platform

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

Developer, affiliate, and collaborator payouts follow the same 1st and 15th schedule. Eastern sales from the 1st through the 15th are assigned to the following month’s 1st payout run. Sales from the 16th through month end are assigned to the following month’s 15th run, at 08:00 America/New_York. This is an approximately two-week wait after the assigned sales period, including short February dates. The customer refund policy remains 14 days. Later refunds are deducted once from the next payout, with any uncovered remainder carried forward. Unpaid periods remain separate; these are payment-initiation dates, not guaranteed arrival dates.

Product prices, checkout charges and accounting remain USD. Eligible Stripe destinations can quote local-currency bank settlement; PayPal developer payouts use USD. Destination-country requirements and payout-provider costs remain separate from checkout processing.

SoundSync

Choose and verify a payout destination

  1. 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.

  2. 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.

  3. 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.

  4. Verify PayPal separately if chosen

    Use the payout email you own, which can differ from the login email. Confirm the email with PayPal and complete its account requirements, then verify the eight-digit SoundSync inbox code. Supply the registered PayPal country and confirm the account can receive USD. PayPal Payouts is approved; inbox verification alone does not establish recipient eligibility. SoundSync never asks for your PayPal password.

  5. 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

Payout history

Current history interface with example records, not proof of a payout.

SoundSync

Verify the destination before saving it

The destination form separates the payout provider, registered country and required account information. This example does not save a destination, verify recipient eligibility or complete a payment.

Payout destination - Example data; no live transaction or account change.

Sale earnings and the received payout are different

Actual checkout processing fees are billed separately to the developer; external sellers pay their own providers. 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 has a $1.47 SoundSync fee and $47.53 in sale earnings before actual processing charges and any agreed affiliate/collaborator allocation. The payout preview then shows applicable sending costs, invoice offsets and other recorded adjustments to the eligible balance.

For current eligible Stripe international quotes under the November 18 confirmed policy, the cross-border rate is 0.25% of the USD transfer before FX. Conversion is 1%, with any quoted rate-lock premium recorded separately. The default uses the fee-inclusive quoted exchange rate: these FX costs are not withheld again in USD. An independently verified separate-billing tariff instead uses its recorded USD withholding and fee-free settlement rate. Standard payout and active-account costs remain separate itemized components, not another marketplace charge.

A confirmed rate is not a final provider bill or bank receipt. Monthly USD fee accruals retain fractional precision; displayed cent deductions are provisional until attributable provider invoices, credits and settlement evidence are reconciled. Differences debit or credit a later payout without charging the same fee twice. Historical quotes retain their saved fee treatment. Inspect the recorded FX treatment rather than inferring it from the account fee-payer setting; never subtract an FX component again when it is already included in withholding or the saved quote.

SoundSync

Read the payment stage, not just the total

StageWhat it establishes
Next-run estimateShows recorded earnings assigned to that Eastern sales-period run, less applicable deductions. Later-period earnings remain separate. It is not a completed payout.
Processing costs still being verifiedKnown sales and usage can remain visible while the payout estimate is incomplete. An unavailable amount is not zero, and this forecast does not release funds.
Billing needs reconciliationClosed-period usage, processing charges, invoices or recovery records may need reconciliation before a payment can be calculated. A previously prepared amount can also need a fresh billing check.
No bank payment for the inspected runThere may be no payable bank amount, or eligible earnings may be fully applied to documented deductions. Inspect any remaining recovery separately; this state does not mean a bank transfer was completed.
Approved or submittedThe amount is scheduled or submitted to a provider; it has not necessarily reached a bank.
Stripe transferFunds reached the connected account. The bank-payout step and bank status are separate.
PayPal pending or unclaimedThe payment has not been confirmed as received. Resolve the actual provider status or recipient requirements; do not treat submission as success or send it again blindly.
Fee reconciliationProvider-reported fees can settle an earlier estimate and appear as a later debit or credit.
History and CSVUse 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

Payout Setup API

Owner-only destination and verification calls; no payment-sending endpoint.

Statements and settlements

Monthly minimum, held balances, offsets and closeout.

Payout policy

Schedule, funds, eligibility and destination boundaries.

SoundSync

Payout setup response states

Response or inputNext step
verification.status: pendingThe code has been sent, not verified. Enter the current code for the same email and environment.
verification.status: verifiedVerification succeeded. Saving the payout destination is still a separate action.
verification: nullThe 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_failedUse the returned error or current verification state. Respect the cooldown and hourly limits before requesting a new code.
confirmPayPalAccount: trueRequired when selecting PayPal. Confirm ownership and ability to receive USD; use the actual registered PayPal country.
paypalEmail / emailpaypalEmail 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.

Read actual checkout fees before the payout estimate

Actual checkout processing is a separate developer cost. An already collected invoice and an invoice offset must not both deduct the same charge. Missing provider evidence is pending; the payout estimate can remain unavailable until reconciliation.

If an unsettled local-currency quote expires, its FX fee, rate and net amount are no longer current. Refresh the quote before reviewing payment; expiry does not approve a payout or contact the provider automatically. A completed payment retains its actual receipt.

A current forecast is not authorization to send

The payout forecast combines sales and recorded fees for the selected Eastern payout period with its estimated usage and actual processing. It can be available before billing is finalized or a payout is ready. Known sales and usage remain visible while processing is pending; the unknown processing, final deductions and net amount remain unavailable rather than zero.

Forecasted net is before payout-provider costs. A provider fee preview can estimate the later payment, but neither the forecast nor its displayed destination approves or sends funds. A negative forecast identifies an estimated amount due, not a negative bank transfer.

An upcoming forecast does not replace an unpaid payout

The developer summary follows the upcoming payout run and its assigned sales period. An older unpaid payout keeps its original period and remains owed; it is not silently added to the new forecast or erased when the schedule advances. Payment preparation reviews the oldest unpaid period separately.

Earnings shown as held can belong to another sales period or have a specific hold. Compare the displayed period, payout history and total unpaid balance before treating held earnings as missing. The forecast is not the amount already sent or received.

Read the allowance across both payout periods

The payout breakdown shows free usage consumed through the selected period end and paid units inside that period. Earlier usage in the same Eastern month still consumes the same allowance; a new payout window does not supply another 1,000 emails or 10,000 redemptions. Multi-month ranges combine the separate monthly allowances.

Estimated payout-provider fees appear with the expenses before total deductions and the final payout amount. Open the row details for country, provider, currency and applicable FX information. This presentation does not change the allowance, sales-fee minimum or payment eligibility.

The payout aliases do not grant extra authority

The earnings, settlements and payouts URLs share the same setup and reporting handlers. Choosing another mount cannot bypass workspace ownership, live/test approval, verified payout-email proof or billing access. Owner-only setup stays owner-only. A saved destination, refreshed status, transfer record and confirmed bank receipt are different states.

SoundSync

Complete payout compatibility map

Billing and Settlements API

Every supported router alias, its preferred contract and report-specific filters.

Use the current payout-history CSV

The private export has 38 ordered columns. The first 33 retain their positions, including fee, FX and reconciliation evidence. Five appended columns identify the Eastern sales-period start and inclusive end, closeout audit ID, related canceled draft IDs and settlement method. Read the CSV header rather than assigning columns by an older position. The export follows the combined chronological history, not a separate list of batches followed by closeouts.

An empty actual-fee value is unavailable, not a confirmed zero. A confirmed rate can still have provisional monthly withholding. The FX-included flag distinguishes explicitly verified separately billed costs withheld in USD from fee-inclusive quotes, which are the current default; do not subtract either component twice. The recorded rate prefers verified settlement evidence, then the saved settlement rate under its recorded fee treatment, then a historical quote. Conversion status can be quoted, expired_quote, confirmed or unavailable; no FX record leaves the column empty. A missing or invalid expiry must not be labeled as a valid quote. Confirmed conversion is separate from confirmed bank receipt.

Provider notifications reconcile an existing payment

Where supported provider notifications are configured, SoundSync verifies the notification and checks the recorded provider payment before updating its status. A notification does not initiate a new payout. A returned or refunded payout is a recipient-payment issue, not a customer product refund; recorded returned principal and destination review remain separate from product access.

Eligible provider-fee revisions are recorded as later corrections without rewriting an adjustment already applied to an earlier payout. Repeated evidence is not another charge. Owner-confirmed fee differences or incomplete provider evidence can still require review.

Follow one chronological history timeline

entries is the combined, paginated history of batches and verified no-cash closeouts, ordered by creation time newest first. A closeout comes before a batch with the same timestamp, then IDs sort descending. Use kind plus id as the record key. batches and bookkeepingCloseouts describe the same page, not two extra lists to append. hasMore and offset apply to entries, even when a page has no batches.

from and to include the selected Eastern calendar days (America/New_York) of history-event creation, not the sales dates. For example, 03:30 UTC on November 16 falls on November 15 Eastern. Source-sale times use order occurrence, falling back to creation time; the scheduled run stays a date-only value. CSV exports all matching timeline pages and adds separate Eastern sales-period columns.

A closeout can explain a canceled draft without a payment

An owner_closeout entry contains a verified bookkeeping record. Its paid accounting status does not mean cash was sent: noPaymentSent is true and cashMovementCents is zero. It has no bank-payment receipt. A canceled batch can carry bookkeeping_closeout linking to the same audit record even when that closeout is outside the current page or date range. Do not count the canceled draft and closeout as two payouts or retry either as a payment.

CSV labels these records owner_bookkeeping_closeout_no_cash and canceled_draft_closed_by_owner_bookkeeping. A closeout leaves UTC sale columns empty and supplies its Eastern period with an inclusive end date, audit ID and related canceled drafts. Normal batch rows use payout_batch. An empty provider reference is not evidence of a missing transfer that should be recreated.

Follow a linked history record

A payout-history link to a batch or owner bookkeeping closeout opens the matching record and its disclosure panels when that record is on the loaded page. A reference outside the page remains a reference; adjust the history range or pagination to locate it. A canceled draft linked to a no-cash closeout is not a second payment.