Refund, Revision and Dispute Basics for White-Label Client Packages

Refunds are awkward for anyone who sells digital work, and more so for agencies and coaches selling rebranded white-label packages. The files cannot be “returned,” the client may already be using them, and much of the value is in the customization you did. Clear written terms will not prevent every disagreement, but they make most of them shorter and give you something concrete to point to if a client disputes a card payment.

This guide covers what to put in writing and what payment processors say about evidence, using Stripe’s published guidance as an example. It is general information only — refund rules and consumer protections vary by state and country, so have a qualified attorney review your own terms.

Why Client Packages Need Their Own Policy

A shop that sells a downloadable ebook can usually describe its refund policy in a sentence or two. A client package is different because it mixes three things:

Licensed material that exists before the project starts.
Your service time — rebranding, editing and adding client-specific sections.
Delivered files that the client can keep using after delivery.

A useful policy treats each part separately, so “refund” has a defined meaning at each stage of the project rather than an all-or-nothing answer.

What to Put in Writing

Refunds by Project Stage

Spell out what happens if the client cancels at each stage. One illustrative structure — an example, not a recommendation for your business:

Before work starts: deposit refunded in full or in part, as you specify.
After the first draft is delivered: deposit retained to cover work completed.
After final files are delivered: no refund, but revisions handled under the revision terms.

Whatever you choose, make the stages match the milestones on your invoices so there is no gap between what the proposal says and what the client paid for.

Revision Rounds

Many refund requests are really revision requests. State how many rounds of changes are included, what counts as a revision (wording, colors, swapping images) versus new scope (extra pages, a second product), and how quickly the client needs to send feedback. Offering a fix before a refund keeps the conversation practical.

What the Client Receives and May Do

Describe the deliverables, file formats and the usage rights the client gets, consistent with your white-label license. If the license does not let the client resell or redistribute the files, say so. This protects you with your provider as much as with the client.

How to Present the Policy

Stripe’s dispute prevention best practices (checked October 2026) recommend including a clear description of refund and cancellation policies in your terms of service and requiring customers to agree to them. Stripe adds a detail that matters for invoices: card issuers can be specific about how policies were presented, and a checkbox containing only a link may not be accepted as sufficient evidence that the customer saw the policy. Stripe suggests showing the full policy at checkout or in a pop-up the customer must agree to before ordering.

For client projects, practical equivalents include:

Including the full refund and revision terms in the proposal or contract the client signs, not only a link.
Repeating a short version, with the stage-by-stage refund rule, in the invoice notes.
Keeping a copy of the signed proposal with the client’s record.

Make Your Charges Recognizable

Some disputes start because a client simply does not recognize a charge. Stripe recommends using your website domain or business name as the statement descriptor, which it limits to 5–22 characters. If you run more than one business, Stripe also advises using a separate account for each so descriptors and contact details stay distinct. For agencies that bill under one company name but deliver work under a client’s brand, it helps to mention your company name in the proposal and invoice so the charge matches what the client expects.

Keep Evidence as You Go

Stripe’s dispute categories guide notes that digital products and services usually lack shipping records, so the evidence should focus on usage, login or download. For digital products or services, the evidence Stripe lists includes:

The text of the refund or cancellation policy as provided to the customer.
An explanation of how and where the policy was shown before purchase.
Your explanation of why the customer is not entitled to a refund, if that is your position.
Communication with the customer, such as email exchanges, and whether they contacted you before disputing.
Whether the customer used the product or service in whole or in part.

For a white-label package, that means keeping a simple project log: the signed proposal, dated delivery emails or file-share records, approval messages, and revision requests. A consistent handoff routine makes this record easier to keep.

When a Client Asks for a Refund

Reply quickly and ask what is not working; offer the revisions the agreement includes.
If a refund is due under your terms, issue it promptly. Stripe notes that responding to issues and processing refunds quickly makes customers less likely to file a dispute.
Be aware that, according to Stripe, a partially refunded payment can still be disputed — and card network rules can allow the dispute for the full amount — so document any partial refund agreement in writing.
If a dispute arrives anyway, respond with the evidence above rather than argument alone.

A Short Checklist

Refunds defined by project stage and matched to invoice milestones.
Revision rounds and scope limits stated.
Client usage rights consistent with your white-label license.
Full terms in the signed proposal, summarized on the invoice.
Recognizable statement descriptor.
Project log of approvals, deliveries and messages.

Processor rules and card network rules change, so check your payment processor’s current documentation, and ask a qualified attorney to review your terms for the places where you and your clients do business.