Studio Queues Team · Last updated June 24, 2026
Learn how to prevent chargebacks and protect your commission work with a prevention stack including click-to-accept TOS, milestone payments, in-platform
A client paid you three months ago. The work was delivered. They said thanks. They went quiet. This morning PayPal sent the chargeback notification.
The $400 is already gone. The $20 dispute fee is on top. You have screenshots from Discord, a delivered file, and a sinking feeling. The bank wants proof the client agreed to your terms, proof they received the work, proof of the scope. You have some of this, not in the format the bank wants, and you have until next Tuesday to submit it.
If this is happening to you right now, skip to the bottom section first. The rest of this article is the prevention stack so the next one doesn't happen.
Three patterns account for most of them.
Friendly fraud. The client received the work, was satisfied, and disputes the charge anyway. Sometimes it's a partner or family member who saw the credit card statement and asked "what's this for." Sometimes it's the client themselves discovering that chargebacks exist and trying one on. Industry estimates put friendly fraud at over half of all chargebacks across digital products. It's the most common, the hardest to predict, and the one that prevention layers actually help with.
Buyer's remorse disguised as a dispute. The client decided weeks later that they don't want the work after all. Instead of asking for a refund (which they probably wouldn't get), they file a chargeback claiming "service not as described" or "did not receive." The bank doesn't know the difference. The evidence either supports the merchant or it doesn't.
Genuine fraud. The card used to pay was stolen. The real cardholder files the dispute. This is the rarest of the three and the hardest to prevent because the fraud happened upstream of you, but it's worth knowing it exists.
In all three cases, the chargeback is decided based on what evidence each side can present. The card network has a process called representment where the merchant responds with compelling evidence. The threshold for "compelling" varies by network and dispute type, but the categories are predictable: proof of agreement, proof of delivery, proof of communication, and proof of scope. The prevention stack is structured around making each one bulletproof.
Quickly, because the rest of the article is about prevention:
You can respond. The processor will give you a deadline, usually 7 to 10 business days for the first response. You submit the evidence you have through their dispute interface. Most processors auto-pull what they can and ask you for the rest.
You can win. Chargeback win rates vary, but with proper evidence the rate is much higher than without. The categories of evidence that hold up best are listed in the next sections. Even if you don't have everything in the ideal format, send what you have.
You can't undo it. The chargeback is filed. The money is already on hold. The dispute process determines whether it comes back to you. There's no shortcut around the process.
You can't usually appeal a loss directly with the customer. Once the bank rules against you, the customer doesn't owe you anything. Small claims is an option for larger amounts but rarely worth the time for typical commission values.
The lesson most artists take from a lost chargeback is "I need to set up prevention before the next one." Which is the actual point.
Five layers. Each one reduces the chance of a chargeback being filed in the first place, and improves your evidence if one is filed anyway.
The single most important piece. Without an enforceable TOS, your refund policy, scope policy, and revision policy aren't binding even if they're well written. The bank treats your linked-in-bio TOS as a suggestion, not a contract.
A click-to-accept TOS records the moment the client agreed, the version of the terms they agreed to, and a timestamp. That record is the strongest single piece of evidence in a chargeback dispute. It moves the case from "did they agree?" to "they agreed at 2:47 PM on March 14 to these specific terms."
Studio Queues records the click on every commission submission by default. The TOS version, the timestamp, and the commission record are tied together. When a dispute comes through, the evidence is one search, not an email archaeology project. The full explainer on why a linked TOS doesn't hold up is in click-to-accept TOS for commission artists.
If you're not on a platform, you can build the same record with a checkbox on your intake form plus an automated email at submit time, but the records are usually weaker because they're scattered across tools you're maintaining yourself.
A $600 commission paid up front is one chargeback opportunity worth $600. The same commission split into three milestone payments of $200, $200, and $200 is three smaller transactions, none of which is large enough on its own to be worth the friction of disputing.
This isn't just psychological. It also means that if a dispute is filed on one milestone, the others are usually unaffected. You lose $200, not $600. And the evidence for each milestone is cleaner because it's tied to a specific deliverable that the client signed off on.
Studio Queues handles milestone splits at the intake stage. You set the split (30/30/40, 25/25/25/25, whatever the project needs) and the payment release happens at each stage with the client signoff. You're not running multiple Stripe invoices or manually tracking who's paid what. The structure is the same one used on vtuber commissions and any other staged work where the deliverable comes in phases.
Manual milestones are possible but painful. Multiple Stripe payment links, a spreadsheet tracking what released when, manual emails confirming each phase. Every place in that stack is a place where the record can break.
Most artist communication happens in Discord. Most evidence submitted in chargeback disputes is Discord screenshots. There are three problems with this.
First, screenshots are easy to fabricate, and the bank knows this. They're treated as weaker evidence than messages from a system with verifiable timestamps.
Second, Discord messages disappear. Servers get deleted. DMs get cleared. Accounts get banned. Six weeks after delivery, the conversation you screenshotted may not exist anymore.
Third, Discord scatters the conversation. Some of it is in DMs, some in a server, some in voice transcripts you don't have. There's no single thread you can produce as the record.
In-platform messaging on Studio Queues keeps every exchange about a commission tied to that commission record. The timestamps are server-recorded. The thread is preserved with the project. When a dispute comes through, the communication evidence is the thread, not a stack of screenshots.
If you're not on a platform, the workaround is to mirror every meaningful Discord conversation to email or your own log so there's a verifiable backup. Most artists don't do this, which is why screenshots are the default evidence and why screenshot evidence keeps losing.
The "did not receive product" chargeback category is one of the most common for digital work, because banks default to assuming the customer is right when there's no clear proof of acceptance.
A signoff at each milestone is the proof. The client receives the milestone deliverable (sketch, lineart, expression set, whatever the phase is), reviews it, and explicitly confirms acceptance before the next milestone begins. The confirmation is timestamped and tied to the commission record.
This serves two purposes. It produces evidence that the client received and accepted the work at each stage, which is exactly what the "did not receive" defense needs. And it prevents scope drift by forcing the client to commit at each phase instead of leaving things vague.
Studio Queues' milestone structure includes signoff at each release. The client confirms before the next phase starts. The acceptance is recorded with the commission. Manual setups can replicate this with explicit email confirmations at each phase, but the workflow has to be enforced consistently or it falls apart.
The strongest payment protection available, with real friction trade-offs.
Stablecoin payments through a smart contract escrow (USDC on Base, in Studio Queues' implementation) are non-reversible at the protocol level. There's no chargeback mechanism because there's no card network in the loop. The funds sit in escrow controlled by the contract until the milestone releases trigger them.
For a $400 character portrait, this is overkill. For a $4,000 vtuber package or a high-value commercial commission where a chargeback would meaningfully hurt, the trade-off is worth thinking about.
The trade-offs are real:
Studio Queues offers crypto escrow alongside Stripe at the booking stage, so the client picks which one. You don't run a separate workflow for the crypto commissions. For most commissions Stripe with the layers above is enough. For the ones where the dollar amount makes a chargeback genuinely scary, crypto escrow is the option that exists.
Each layer reduces chargeback risk in two ways. It makes a dispute less likely to be filed (smaller transactions, clearer agreements, better communication), and it makes your evidence stronger if one is filed anyway (timestamped acceptance, signoff records, verifiable messaging).
You don't have to stack the layers yourself. The brief from the start of this article ("every layer is in Studio Queues by default") is the actual product positioning, and it's true. Click-to-accept, milestone payments, in-platform messaging, deliverable signoffs, and optional crypto escrow are all part of the platform you'd use to manage the commission anyway. You're not adding a chargeback prevention tool on top of your workflow. The workflow is the prevention.
If you'd rather build the stack manually, every layer is replicable. It's a lot of pieces to maintain, a lot of places for the records to break, and a lot of upfront work, but the layers themselves are not exotic. The trade is hours of setup and maintenance versus the structure being there by default.
If you got here because you're actively in a dispute, the immediate steps:
Find the deadline. Your processor will have set one, usually 7 to 10 business days for the first response. Don't miss it. Missing the deadline is the same as conceding.
Pull every piece of evidence you have. TOS agreement records (if any), delivery proof, every relevant message exchange, payment records, scope documentation. Even if it's scattered, gather it.
Submit through the processor's dispute interface. PayPal, Stripe, and others have specific forms for this. Follow their format exactly. Add a clear written summary of what was delivered, when, and what the agreement was.
Keep records of the dispute itself. Whatever you submit and whatever the processor responds with. If this becomes a pattern with the same client across multiple platforms, the record matters.
Don't escalate with the client. A hostile reply to a chargeback notification rarely helps and sometimes hurts. The bank decides. Submit clean evidence and let the process run.
You may lose this one. Use it as the trigger to set up the prevention stack so it's the last one.
Chargebacks on commission work aren't avoidable in absolute terms. Clients do unpredictable things, banks default to customer-favorable rulings on ambiguous cases, and friendly fraud is a real ongoing rate even with perfect setup. What you can do is move yourself from "easy target with screenshots" to "documented merchant with timestamped evidence at every step."
The five layers above are what that looks like in practice. Run on a platform that has them built in or build them yourself with a stack of tools and discipline. Either path gets you to the same place: when a dispute comes through, the evidence exists, the response is fast, and the win rate goes way up.
You probably still lose some. You lose a lot fewer.
