Direct answer

They accepted it. Now they want a refund. Start with the record.

A refund request that arrives after acceptance is really two different requests wearing one coat. One says the work fails the agreement, which is fixable and checkable. The other says the client changed their mind after checking and accepting the work, which is a request to undo a finished decision. The acceptance record is what tells them apart, and it is what your reply should be built on. Here is the full response, in order.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 18, 2026. The acceptance record quoted below is real and public, read back from the live service on publication day.

Step 1. Sort the request before answering it

Three cases cover nearly every refund request. A genuine defect: the work does not match the written agreement in a way the client can point to. The remedy is a fix, and if a fix is impossible, a refund for the failing part. A changed mind: the work matches the agreement, the client checked and accepted it, and they have since decided they do not want it. Nothing failed; a preference moved. Budget regret: money got tight, and the refund request is really a renegotiation. It usually presents as a vague quality complaint, which is why the sorting question matters: ask, in writing, which specific part of the work fails the agreement. Defects can always answer that question. The other two cases struggle to, and naming that difference, politely, is most of the reply.

Step 2. Read the acceptance record out loud

If the work was delivered as a record, acceptance is a state with a date, not a memory. A real example, read back from the live service on publication day:

What an accepted delivery looks like from the record

Hold that card up against the opposite state, a handover still pending with release state hold, and the difference is the job: one client decided, the other has not yet. A refund request against the first card has to argue with the client's own recorded decision. A refund request against work with no acceptance at all argues with nothing, which is exactly why sellers without records end up refunding work that was fine.

Step 3. Send the reply that carries the record

One message, four attachments in effect: the agreement, the delivery record, the acceptance state with its date, and a standing offer to fix any specific part that fails the agreement. Keep the tone level and the length short. You are not arguing that the client is wrong to be unhappy; you are showing the sequence both sides already walked: work delivered, work checked, work accepted, payment released. Then stop. A record-based reply said once is stronger than the same reply defended across ten messages, and every extra message is a fresh chance for the conversation to become about tone instead of facts.

Step 4. Decide the goodwill question separately

Whether to offer a partial credit is a business decision, not an evidence question, and it goes better decided on its own. Credits buy goodwill with clients worth keeping and can be cheaper than a platform dispute or a card chargeback fight, where the acceptance record is also your core evidence if it comes to that. What a credit should never be is the automatic price of ending an uncomfortable conversation: a client who gets a discount for complaining after acceptance has been taught a sequence, and sequences get repeated.

What the record does not decide

An acceptance record proves the saved result was not changed since it was saved, and it proves the client accepted the delivery on a stated date, with the release state that followed. It does not prove the work was good, and it does not override the law: consumer protection rules in some places give buyers refund rights that no private record can remove, and platform terms can impose their own refund process. This page is general information, not legal advice. What the record does is shrink the dispute to its honest size: one specific claim about the work, tested against the agreement, instead of a general undoing of a finished job.

Set up the next job so acceptance comes first

The durable fix is sequencing. Deliver as a handover the client checks and accepts or flags before final payment, so scrutiny happens while it can still change the work. Write the acceptance test into the agreement: what the client checks, how long they have, and what acceptance releases. After that, a refund request is no longer a surprise genre of email; it is a claim against a recorded decision, and it gets answered that way.

Frequently asked questions

My client wants a refund after accepting the work. What do I do?

Start by sorting the request into one of three cases. A genuine defect means the work does not match what was agreed: fix it or refund that part, promptly. A changed mind means the work matches the agreement and the client accepted it, then decided they did not want it: that is not a defect, and the acceptance record is your answer. Budget regret wears the clothes of the other two, so ask which specific part of the work fails the agreement, in writing. Then reply from the record: what was delivered, when the client checked it, and the acceptance state with its date. Offer the fix for anything genuinely wrong, and hold the line on the rest, calmly and once. This page is general information, not legal advice, and consumer rules in some places give buyers extra rights, so check yours before relying on any general sequence.

Does acceptance actually change anything, or is it just a formality?

It changes the question under discussion. Without an acceptance, a refund request opens everything: was the work delivered, was it the work agreed, did the client ever see it. With a recorded acceptance, those questions are already answered by the client themselves, and the only live question is whether the work fails the agreement in a specific way the client can name. That is a much smaller conversation. Acceptance here means a recorded decision on the delivery record: the client opened the handover, checked the steps, and accepted, which flips the release state to ok_to_release with a date attached.

What exactly should I send back when a client asks for a refund?

One short message carrying four things: the agreement and what it promised, the delivery record showing the work step by step with its times, the acceptance state showing the client accepted it and when, and your offer to fix any specific part that fails the agreement. Ask the client to name the failing part in reply. That request does real work: a genuine defect can always be named, and a refund request that cannot name one usually resolves into a negotiation about a fix or a partial goodwill credit, on your terms, instead of a full refund on theirs.

Should I ever offer a partial refund or credit?

Sometimes, as a business decision, with your eyes open about what it buys. A partial credit can keep a good client who hit a genuine budget problem, and it is cheaper than a platform dispute or a chargeback fight. It buys nothing when the pattern is pressure: a client who learns that acceptance followed by complaint produces discounts will repeat the sequence. Decide by the record, not the volume: a named defect gets a fix, a valued relationship can get a credit, and a refund for accepted work that matches the agreement gets a polite no with the acceptance record attached.

How do I stop refund requests like this on the next job?

Move the decision to before the money. Deliver through Zambo as a handover the client checks and accepts or flags, and make final payment follow acceptance, so the client spends their scrutiny while it can still change the work, not after. The acceptance is recorded against the delivery itself, with the release state and date, which is the document a later refund request has to argue with. For $0.99, put the next delivery behind an acceptance your client records before the final payment, so a later refund request meets the record first: get the Day Pass. A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related