Documentation
Test the Customer Experience
Rehearse verification, recovery, paid and free access, downloads and plugin activation using one test customer.
SoundSync
Use one customer throughout
-
Prepare your customer
Before Start guided test, choose an unused test email or keep the developer email default. Copy the separate customer login fields; the developer password is not a customer password. Keep your developer window signed in.
-
Verify and sign in
Open Customer website in another tab. Use the customer verification link from Test inbox or the supported mailbox copy. Sign in, sign out and test recovery. Customer sessions are scoped to the test storefront, separate from the developer session.
-
Make a sandbox purchase
Use fictional billing details and the guide’s configured payment sandbox. Stripe test checkout shows 4242 4242 4242 4242, a future expiry and a three-digit CVC. Choose from the configured country/state list and inspect the tax quote. Never use a real card or a production payment account.
-
Claim the free product
On the free product page, choose Get it free after verified customer sign-in. This bypasses payment, not account ownership checks. Repeat the claim to check that existing access is reused.
-
Inspect the library
Wait for verified purchase fulfillment. Each sample has its own acquired serial and authorized private source download. A provider return page alone is not proof of ownership.
-
Activate the matching product
Build its JUCE package. Account uses customer email and password; Serial uses the acquired serial and email. Exercise validation, private downloads, Store, My Products, offline behavior and online deactivation.
-
Review advanced states
Use the normal test customer/licensing tools to check expiry, revocation and sandbox refunds. Observe each result; following a navigation link does not mark a test as passed.
SoundSync
Use the same test customer in the plugin
Your private Test inbox
The inbox shows the latest 100 workspace messages, including verification, recovery, purchase and license activation. Captured HTML is shown safely as text with allowed action links. The owner can read these private messages; other developers and team members cannot use the owner inbox. Passwords, links and serials are private even in a test environment.
A mailbox copy has a narrow destination
When the dedicated evaluation mail transport is configured, supported transactional messages addressed to the SSO-verified developer email can also be submitted to that mailbox. Arbitrary test addresses and marketing previews remain capture-only. The interface shows capture/submission state and configured delivery availability; submitted does not mean delivered. Send email check exercises this route, subject to its limits. Reopen through the live dashboard when the verified mailbox changes.
Replace a customer without erasing old access
Generated credentials remain until explicit replacement. Create replacement customer preserves previous customer records, logins, purchases, licenses and downloads; it requires an unused address instead of overwriting someone else’s password. After customer password recovery, the old generated password is hidden. Use the new customer-chosen password. Generated passwords are encrypted at rest and are never bundled into plugin binaries or source ZIPs.
Tax rehearsal is not a tax registration claim
The cart uses configured country and regional test rules. The guide’s billing example is optional, not a restriction to one destination. Unknown or unconfigured destinations are not evidence of a zero tax rate. Test quotes, simulated location evidence and sandbox receipts do not establish live registrations, filing or remittance.
