A mixing or mastering engineer can get paid before delivering final audio stems by separating review files from production files. Send a limited preview for approval, collect the agreed balance, verify payment, then unlock the versioned WAV package.
This is a client-delivery workflow, not a guide to reusable sample packs.
Define Approval and Delivery Separately
| Milestone | Client receives | Payment state |
|---|---|---|
| Review | Streamable preview or marked reference | Deposit paid; balance may remain |
| Final delivery | Full-resolution masters and agreed stems | Cleared balance |
Do not degrade the preview so much that approval is impossible. A spoken watermark, short silence, reference file or private stream can protect the deliverable while preserving a real decision.
Create a Stem-Delivery Manifest
| Field | Example |
|---|---|
| Project | Artist – Track – Mix 4 |
| Main master | 24-bit, 48 kHz WAV |
| Alternate | Instrumental WAV and MP3 reference |
| Stems | Drums, bass, music, lead and backing vocals |
| Alignment | All begin at 00:00 and have equal length |
| Processing | Mix-bus processing printed; stem sum tested |
| Checksum | SHA-256 for the final ZIP |
This original practical artifact identifies the approved release without filenames such as “final-final-2.wav.”
Export and Rebuild the Package
Export every file from the same session start and sample rate. Import delivered stems into a blank session, set faders to unity and compare with the approved mix. Note intentional differences caused by mix-bus processing, automation or side chains.
Open the ZIP on another device. Check duration, channels, clipping, metadata and names. Never promise stems recreate the master exactly unless tested.
Collect the Balance Without Exposing Masters
- Send review material and request written approval.
- Record the approved revision and deliverables.
- Create a customer-specific payment page or invoice for the balance.
- Upload the ZIP behind payment-confirmed delivery.
- Verify provider success, not a screenshot or pending state.
- Release the package and retain payment and delivery events.
PayRequest's file-delivery feature supports files up to 25 GB and is built for “pay before download.” For reusable products, use the music and audio workflow.
Handle Revisions and Disputes
State included revisions, what counts as a revision, when approval is final, availability duration and what happens when replacement recordings arrive. Keep dated approvals and the manifest. A log cannot guarantee a dispute outcome, but it clarifies what was approved, paid, released and accessed.
Complete the Clean-Client Test
Use a new email to open the review, pay a test invoice and download the ZIP. Confirm failed and pending payments reveal no masters, successful payment delivers the manifest checksum, and the archive opens on mobile and desktop.
Then get paid before releasing final audio with PayRequest.
Send only review material required for approval. Release full-resolution masters and stems according to the written milestone.
Deliver the promised formats. Common options are a WAV master, MP3 reference, instrumental and named, time-aligned stems.
Yes. A pay-before-download workflow connects customer payment to protected delivery; verify its current size limit before upload.