To get paid before sending final files, let the client approve a non-usable preview, make the remaining balance explicit, verify the payment in your own account, and release the production files only after that verification passes. The client gets proof that the work is ready; you keep control of the deliverable until the agreed payment event occurs.
This workflow suits designers, photographers, video editors, audio professionals and other freelancers whose final files have immediate value. It is not a substitute for a contract, and it should not override net terms or delivery rules you already accepted.
Use a Release Gate, Not a Last-Minute Surprise
A release gate is one documented checkpoint between approval and delivery. Define it in the proposal or statement of work, not after the client asks for the files.
| Gate item | Pass condition | If it fails |
|---|---|---|
| Scope | Deliverables and included formats match the agreement | Quote extra work or correct the package |
| Approval | Client approves the preview in writing | Keep the project in review |
| Amount | Final invoice shows the agreed balance and reference | Reconcile the invoice before requesting payment |
| Payment | Transaction appears with an actionable paid status in your account | Do not rely on a screenshot or forwarded email |
| Delivery | Final package opens and contains the promised files | Rebuild and test the package |
The gate protects both sides when its conditions are visible. It prevents a freelancer from demanding an unexpected payment step and prevents a client from treating a review copy as the complete handoff.
Decide What the Client Can Review Before Payment
Show enough to support a real approval, but do not send the asset that completes the client's job. The right preview depends on the work.
| Freelance work | Useful review copy | Hold until release |
|---|---|---|
| Logo or brand design | Watermarked presentation and flattened mockups | Vector source, font files and production exports |
| Photography | Watermarked gallery or reduced-resolution proofs | Full-resolution edited files and print license |
| Video | Watermarked review link or compressed preview | Clean master, captions, project files and alternates |
| Audio | Tagged or shortened preview | Full-resolution master, stems and session files |
| Documents or reports | Screen share or protected review PDF | Editable source and clean final PDF |
| Website work | Staging environment with restricted access | Credentials, transfer package and production launch |
A watermark is not a complete security system. Crop, resolution, access controls and the amount of material shown all matter. Do not put confidential client information into a public preview link.
Put the Handoff Terms in Writing
Record the deposit, milestones, revision limit, approval method, final amount, accepted payment methods, due event and exact deliverables. State whether source files, raw footage, fonts, plugins or third-party licenses are included.
Avoid vague phrases such as “files supplied at the end.” A clearer term is: “After written approval of the review copy and receipt of the €600 final balance, the freelancer will provide the listed production files through the agreed download link.” Adapt the language to the actual project and obtain local legal advice for material contracts.
For established business clients, payment may legitimately follow delivery under agreed Net 30 or procurement terms. Do not introduce a pay-before-release gate halfway through that engagement. Use it for new work when both parties accept it, or negotiate a milestone that preserves enough leverage without blocking the client's internal process.
Run the Four-Step Final-File Handoff
Summarize the approved version, included formats and remaining balance in one message. Give the project a stable reference, such as PRJ-1048, and use it on the invoice, payment description and delivery package.
Export the promised formats, remove temporary assets and personal paths, check licenses, scan the archive, and open it on another device or clean user account. Confirm filenames, dimensions, color profiles, codecs or checksums where they matter.
Keep the tested package unchanged after approval. If a correction is necessary, create a new version and record what changed.
Open the connected payment provider or billing dashboard independently. Match the client, reference, amount, currency and live status. A buyer screenshot, bank-transfer promise or email notification can help locate a payment, but it is not the verification source.
Do not confuse a pending, processing, held, failed, refunded or reversed event with a payment you can act on. Provider wording and settlement timing vary, so follow the status and instructions shown for that transaction.
Release the exact tested package, then preserve the delivery time, version, recipient and download or access event when available. Send a concise handoff note containing the file list, any expiry date, installation or usage instructions, support boundary and invoice reference.
Keep the approval, invoice, provider transaction and delivery record connected. Together they explain what was promised, what was paid and what was supplied.
Client Messages You Can Adapt
> The review version for PRJ-1048 is ready at the link below. Please check the agreed content, layout and corrections. This preview is for approval; the production files listed in our agreement will be released after written approval and payment of the final balance.
> Thanks for approving version 3. The remaining balance is €600 under invoice PRJ-1048. Once the payment appears as completed in the agreed payment account, I will release the tested package: print PDF, web exports and source file.
> Payment for PRJ-1048 is verified and the final package is ready. The link contains the three agreed deliverables and expires on 20 August 2026. Please download and back up the files before then. Installation notes and the license summary are included.
Keep the tone procedural. Do not accuse a client of withholding payment when a transfer may still be processing, and never ask them to send passwords, card details or one-time codes.
Automate Payment-Gated File Delivery
Manual delivery works at low volume, but it creates two avoidable failure points: releasing from an unverified notification and forgetting to send the files after a real payment.
With PayRequest file delivery, you upload the final file, set the amount and share one hosted link. The client pays through the available connected provider and unlocks the download through that flow. PayRequest supports files up to 25 GB. The Free plan has no monthly fee; PayRequest charges 2% per successful payment, capped at €25 per transaction, in addition to provider fees. Verify the current terms on the pricing page.
Run one end-to-end test before using the link with a client: open it as a buyer, confirm the offer and amount, complete a real test payment where practical, check the resulting status, download the file on a separate device, and verify that the archive matches the approved package.
Common Handoff Failures
- The preview is usable as the final: reduce its resolution, watermark it or show only what approval requires.
- The client never agreed to the gate: return to the contract and negotiate; do not invent new terms at delivery.
- The amount changed without a signed change: document the added scope before invoicing it.
- A screenshot triggers release: verify the transaction inside your own account.
- The paid package is broken: test the exact archive from a clean device before sharing.
- The link exposes unrelated files: use a dedicated package and review its permissions.
- Delivery has no record: preserve the version, recipient, release time and access evidence.
The goal is not to distrust every client. It is to make approval, payment and delivery observable so neither party has to reconstruct the handoff from scattered messages.