How a freelancer handles a chargeback or payment reversal
The work is done, delivered, and accepted. The money is sitting in your account. Then, weeks later, it isn’t — and nobody asked you first. A chargeback is one of the most disorienting things a freelancer can experience precisely because it happens after the fact, after you’ve already performed, and through a channel you have no direct access to. Understanding exactly how this works, why it happens on completed work, how to fight it, and how to structure your payment setup so it can’t happen at all is the difference between treating it as a recurring hazard and eliminating the risk at the source.
What a chargeback actually is — and why it has nothing to do with you
A chargeback is a forced reversal of a card payment that a customer disputes with their bank, which pulls the money back out of your account after you already counted it as earned. The mechanism was designed as consumer protection — a backstop against fraud, billing errors, and undelivered goods. Chargebacks are a form of consumer protection, originally created to protect people from fraud and unauthorized transactions. The merchant bears the burden of proof. All the cardholder — your freelance client — has to do is contact the bank and ask for their money back.
That asymmetry is the core problem. The card network treats you as a merchant the moment you accept a credit card. If you accept a credit card as a form of payment, even if you are freelancing, credit card companies will deem you a merchant, which means a freelance client can dispute a payment they’ve made to you. The money will be removed from your bank account, without warning or your consent, and you will be left with an extra chargeback fee you’ll have to pay.
Notice what that says. Without warning. Without your consent. The funds move first; the conversation happens afterward, if at all. That is the mechanical reality of chargeback exposure, and no amount of good faith work product changes the underlying rule.
The three types of chargebacks — and which one actually hits freelancers
Not every chargeback looks the same, and the category matters because it determines what evidence you need and what your realistic odds of winning are.
Chargebacks fall into three broad buckets. The first is genuine fraud, where a stolen card was used without the real owner’s knowledge. A second category is a merchant problem, such as undelivered work, a product that did not match the description, or a billing error on your end. Most frustrating of all is so-called friendly fraud, where a legitimate customer disputes a charge they actually authorized.
Genuine card fraud is relatively clean — the card was stolen, the transaction was unauthorized, and while you lose the payment you’re generally not at fault in a moral sense. Merchant-error chargebacks are legitimate grievances: you missed a deadline, the deliverable was materially different from what was scoped, the client genuinely didn’t receive the file. Both of those categories are understandable, even if painful.
The third category is the one that should make every freelancer pay close attention. Friendly fraud, where a legitimate customer disputes a charge they actually authorized, is more common than many freelancers expect. Sometimes the client forgets a purchase, fails to recognize your business name on the statement, or simply tries to avoid paying after the fact.
Sometimes, clients file chargebacks when they feel they’ve received inadequate work; other times freelancers haven’t done anything wrong and the client is trying to get out of paying for the services they requested and received. That second scenario — a client who simply decides after receiving your work that they would prefer not to pay — is not rare. Friendly fraud now drives the majority of eCommerce disputes, accounting for roughly 75% of cases. The fact that it has a soft-sounding name should not obscure what it actually is: theft by card dispute.
How a chargeback unfolds after delivery
The sequence matters. Understanding each step tells you where you have leverage and where you have none.
A chargeback moves through a defined sequence, and understanding it helps you respond calmly. First, the cardholder contacts their issuing bank to dispute a charge instead of asking you for a refund. Then the bank assigns a reason code, reverses the funds, and notifies your payment processor. As a result, the money leaves your account, often before you even know a dispute exists.
Read that again: the funds leave before you know. There is no hearing, no warning email, no opportunity to present your side before the reversal happens. By the time you receive any notification, the money is already gone. Your processor may alert you via email, but that is informational — the reversal has already occurred.
After that, you enter the representation stage, where you can submit evidence to contest the claim. Your processor forwards your documentation to the card network, and the issuing bank reviews it. Finally, the bank rules for you or the customer, usually within 60 to 90 days.
That window — 60 to 90 days — sounds generous until you account for the deadlines you face on your side. Cardholders have up to 120 days to dispute a transaction; merchants have approximately 30 days to respond. Cardholders have around 120 days to file, while merchants only have 20 to 45 days to respond. Four months for them. About a month for you, and often less, because your own processor’s internal deadline typically sits inside the card network’s deadline. The asymmetry doesn’t end with the initial filing.
Beyond the response window, the chargeback also costs you regardless of outcome. A refund is voluntary, since you choose to return the money directly to the customer through your processor. A chargeback, in contrast, is involuntary and routed through the bank, which means you also pay a dispute fee that a refund avoids. The average chargeback costs merchants far more than the $20–$50 processor fee. You lose the disputed amount while the case is pending, you pay the dispute fee whether you win or lose, and if your chargeback rate climbs above the card network’s threshold you risk account termination — meaning you lose the ability to accept cards at all.
The reason code problem
When the bank files the chargeback, it attaches a reason code — a standardized category that nominally explains the basis for the dispute. Common codes that hit freelancers include variations of “services not rendered,” “services not as described,” and “credit not processed.” These codes have enormous consequences for your defense strategy because each one requires a different evidence package.
“Services not rendered” means the client is claiming they received nothing. If you have delivery confirmation — a file transfer receipt, a sent email with attachments, a client approval message — that code is straightforwardly contestable. “Services not as described” is harder, because the bank is now adjudicating whether your output matched a scope of work it has never seen. That is where your contract becomes critical. Many banks and credit card companies view a signed contract as a piece of strong evidence when resolving chargeback disputes, so it can become a strong defence in any such situation.
The problem is that reason codes do not always reflect what is actually happening. Some estimates suggest friendly fraud causes as many as 70% of disputes. A client intending to get your work for free will file under a legitimate-sounding code rather than “I received the work but don’t want to pay.” The bank sees the code; you see a claim you know to be false. Winning requires proving a negative — that the services were rendered, that they matched the description, that the client acknowledged receipt. That proof has to exist before the dispute is filed, because you cannot manufacture it after.
What a strong evidence package looks like
If you receive a chargeback and intend to contest it, the representation stage is your only opportunity. The evidence you submit needs to be organized, factual, and directly responsive to the reason code. Keep your written rebuttal factual and organized rather than emotional. Walk the reviewer through what was ordered, what was delivered, and when, with dates attached to each claim. Card networks reward clarity, so a tidy timeline beats an angry paragraph every time.
Your core documentation package for a post-delivery chargeback should include:
The signed contract or written agreement, including scope of work and payment terms. This is the single most important document. One of the most common causes of chargebacks in the freelance world is the lack of clear contracts or scope of work. When agreements are verbal or vaguely written, they leave room for misunderstandings. This lack of clarity can result in a client disputing a charge because they feel that the work delivered didn’t meet the agreed-upon standards. Without a detailed, signed agreement in place, the door is left open for disagreements that can escalate into chargebacks.
All written communication that demonstrates the project was active, progressing, and delivered — emails, messages, screen recordings of client approvals. If the client signed off, said “looks great,” or asked for revisions and you completed them, that is documented consent to the deliverable. Delivery confirmation: the actual transmission of files, timestamps on uploads, read receipts, version histories. The goal is to prove that something moved from your machine to theirs at a specific time. Any approval of the final deliverable, explicit or implicit. A client who paid an invoice after reviewing work and then files a chargeback weeks later has created a contradiction; your job is to surface that contradiction clearly.
Even with strong evidence, you will not win every case, and that reality is worth accepting before you start. Merchants typically win about 44% of friendly fraud cases. That means a well-documented, correctly filed representation has roughly even odds. It also means roughly half the time you do everything right and still lose, because the bank ultimately protects its cardholder relationship. Issuers may want to close cases as quickly as possible. They may choose the path that resolves the case faster and protects the cardholder relationship. In some cases, that can favor cardholders over merchants.
The copyright clause: a specific lever freelancers often don’t use
For design, writing, illustration, photography, web development, or any creative deliverable, there is an additional defensive tool that operates outside the chargeback process entirely. If you put a clause in your contract stating that copyright transfers to the client only upon payment in full, and the client files a chargeback, they haven’t paid you, and therefore are in violation of copyright laws by continuing to use your design. If you threaten the client with a DMCA takedown, they are likely to cancel the chargeback quickly.
This is not theoretical. A client who uses a contested logo, website, video, or written deliverable while simultaneously claiming they never received it — or received something defective — is in an extremely exposed position the moment you raise copyright. The chargeback may technically still be active, but you have now introduced a separate legal risk for the client that is immediate and independent of the bank’s process. Many clients will withdraw a chargeback rather than face a DMCA notice, particularly if the deliverable is already live on their site or in commercial use. Include the copyright assignment clause in every contract that involves creative output. It costs nothing to add and creates significant leverage if you ever need it.
When it makes sense to fight — and when it doesn’t
Not every chargeback is worth contesting. The decision is primarily financial. You have to weigh the time required to build a proper evidence package against the value of the disputed amount, the processor fee you’ve already paid, and your realistic win probability.
A $150 dispute on a one-off project with a client you’ll never work with again may not justify two hours of documentation assembly when your odds of winning are roughly 44%. A $4,000 dispute on a project where you have extensive written approval of the final deliverable, a signed contract, and a clear delivery trail is absolutely worth fighting — not just for the amount, but because conceding trains future clients that the chargeback path has no consequences.
A chargeback is involuntary and routed through the bank, which means you also pay a dispute fee that a refund avoids. Whenever a customer is simply unhappy, a quick refund is almost always cheaper than letting the dispute escalate. If the client has a legitimate grievance — work that genuinely missed the mark, a deliverable that was materially different from what was scoped — absorbing the loss and addressing the root cause is more efficient than paying dispute fees to contest a case with weak evidence. The distinction matters: fight chargebacks you can document and win; absorb or settle the ones rooted in genuine service problems.
There is also a downstream risk to chargeback frequency that goes beyond any individual transaction. Chargebacks can harm a freelancer’s reputation, lead to higher processing fees, and even result in the closure of their account. Payment processors watch chargeback ratios closely. If your dispute rate breaches the card network’s threshold — typically around 1% of transaction volume — you can find yourself placed in a monitoring program, subjected to higher per-transaction fees, or terminated from the processor entirely. For a freelancer billing primarily through Stripe, PayPal, or Square, a terminated account is a serious operational problem, not just a nuisance.
How to reduce chargeback exposure before it starts
The best chargeback defense is a deal structure that makes a chargeback difficult or irrelevant. This means contracts that are specific enough to remove ambiguity about what was promised, milestone payments that gate future work on acknowledged acceptance of prior work, and delivery workflows that produce a documented paper trail by default rather than as an afterthought.
Milestone structure matters more than most freelancers realize. A single lump-sum payment at the end of a long project creates maximum chargeback exposure: the client has consumed the most work before paying, and the bank sees a single large charge with no documented approval history. Breaking the same project into three or four funded milestones means each payment is smaller, each one is linked to an approved deliverable, and the documentation trail builds incrementally rather than having to be reconstructed under pressure.
Check how your business name appears on customer card statements. Save contracts and delivery proof for every active client. Add written refund terms to your invoices and agreements. The billing descriptor issue is underappreciated. A significant share of chargebacks are initiated simply because the client doesn’t recognize the name on their statement — especially if you operate under a business name different from your trading name, or if your processor uses a parent entity name. Sometimes the client forgets a purchase, fails to recognize your business name on the statement, or simply tries to avoid paying after the fact. Ensuring your statement descriptor is immediately recognizable to your clients eliminates this category entirely.
Payment terms in your contract should include explicit language about what constitutes acceptance, what triggers payment, and what the refund policy is — if any. Clients who sign a contract with a clear “no refunds after delivery and acceptance” clause are substantially less likely to pursue a chargeback, and significantly less likely to win one if they do. A comprehensive, clear, and legally vetted contract can significantly reduce the risk of chargebacks by providing a layer of protection for you. It outlines clear expectations and agreed-upon action in case of dissatisfaction or disagreements.
The payment method question: why card acceptance carries structural risk
The chargeback problem is inseparable from card payment acceptance. Every time a client pays by credit card, you are accepting a payment that carries a reversal window of up to 120 days. The money appears in your account, but it is not irrevocably yours for months. That is not a quirk of one processor — it is a fundamental property of how card networks operate. Every card processor operates under the same card network rules; no contract term, no payment processor policy, and no invoice language you write can override a cardholder’s right to dispute.
Bank transfers, ACH payments, and wire transfers carry a different risk profile — they do not have the same dispute mechanism. Once a wire clears, it doesn’t reverse because a client calls their bank and says they changed their mind. But many clients are unwilling to wire funds to someone they haven’t worked with before, and bank-to-bank transfers can be slow, are difficult to automate, and require sharing banking details that some freelancers prefer to keep private.
The structural answer for freelancers who want payment certainty on delivery — particularly on larger engagements — is to use a payment method where settlement is final by design. When a client pays via a payment link that routes funds directly to a wallet address on-chain, the transaction settles immediately and irreversibly. There is no dispute window. There is no card network with the authority to reverse the transfer. There is no processor holding a reserve against your chargeback ratio. That is where Shaka becomes directly relevant: it is built for professionals who need to close a deal and have the money land — not sit in a reversible pending state for four months. A freelancer who issues a Shaka payment link, gets paid on delivery, and watches the funds route directly to their wallet has closed the chargeback exposure completely. The payment is final the moment it settles.
The scenarios where the math changes
Not every project carries equal chargeback risk. Understanding where your exposure is highest lets you calibrate your payment structure accordingly.
New client, large project, first payment. This is the highest-risk configuration. The client has no relationship with you, the amount is large enough to motivate a dispute attempt, and you have no history of mutual approvals to draw on. This is exactly the scenario where accepting final payment by card carries the most risk and where the certainty of a payment method with final settlement is most valuable.
Repeat client, established relationship, smaller invoices. A client you have worked with for two years who pays a monthly retainer by card is a categorically different risk profile. You have an extensive communication history, a documented pattern of payment and delivery, and a relationship that has social cost for the client to exploit. Card payments in this context carry real but lower risk.
Platform-mediated work with platform payment protection. If you work through Upwork or a similar platform with built-in payment protection, if you qualify for payment protection, your funds will be protected, though they may ask for your help in proving the validity of the charge. But protection is conditional: ultimately, the decision on a dispute is with the financial institution. Platform protection exists, but it is not absolute, and it applies only to work billed through the platform. Off-platform work, direct invoices, and project types that fall outside the platform’s terms carry full exposure.
Digital deliverables vs. physical products. Digital work — design files, code repositories, written content, video edits — is inherently harder to prove delivery on than a physical shipment with a tracking number. A courier scan proves a box arrived. An email with an attached PDF proves it was sent, not that it was received and accepted in good faith. Build your delivery workflow to compensate: send deliverables through channels that log timestamps and read activity, follow up with explicit written requests for acceptance, and document client behavior post-delivery.
The honest bottom line on fighting chargebacks
Chargebacks feel personal when you are the one who did the work, but they are really a documentation problem with a financial cost. You cannot eliminate them entirely, yet you can reduce them to rare events with clear records and fast communication.
That framing is useful and accurate — up to a point. Documentation reduces your exposure and improves your win rate. Contracts, delivery confirmation, milestone approvals, communication records: all of it makes you harder to steal from and better positioned when you do have to fight. But documentation does not eliminate the fundamental structural issue. As long as you are accepting reversible card payments, you are accepting a payment that can be clawed back after delivery, regardless of the quality of your work, the clarity of your contract, or the strength of your evidence.
The freelancers who stop having this problem are almost always the ones who stopped relying on reversible payment rails for their final settlements. Milestone approvals paid by wire, onchain payment links for closing invoices, ACH for retainer relationships where reversals aren’t an option — these are not theoretical alternatives. They are how experienced independent professionals structure payment on work that matters, where the cost of a reversal would be genuinely damaging. The chargeback problem is a payment infrastructure problem, and it has a payment infrastructure solution.
Your contract protects you in a dispute. Your documentation improves your odds. Your copyright clause gives you leverage. But the payment method you choose is the only thing that determines whether a dispute can happen at all. Choose it deliberately.
