# You delivered the work. The payment reversed. What now. A freelancer delivers, the payment clears, then reverses. What the platform does, what the evidence must prove, and what the whole process costs. --- ## You delivered the work. The payment reversed. What now. The money was in your account. You had already moved on to the next project. Then came the notification — not a message from the client, not a request for revisions, but a system-generated alert telling you that a payment you received for work you completed had been reversed. You were not consulted. You were not warned. The decision was made upstream, between a bank and a payment network, and by the time you found out, the outcome had already been set in motion. This is the anatomy of a freelance chargeback — not as a theoretical risk, but as a lived sequence of events with a timeline, a paper trail you probably didn't keep, and a cost you almost certainly didn't price into your rate. ## The Situation Mara is a brand strategist. She works independently, takes on two to four clients per quarter, and delivers brand positioning frameworks, naming systems, and copy decks. Her engagements run between four and twelve weeks. She invoices through a freelance platform and accepts payment by card. Her most recent client was a founder building a direct-to-consumer product. The brief was clear: a naming exercise, a positioning document, and a one-page brand manifesto. They agreed on a fixed price. Mara structured delivery across two milestones, submitted everything on time, incorporated one round of revisions, and received written confirmation from the client that the final deliverable was accepted. Both milestone payments cleared. She withdrew the funds. Six weeks later, the reversal notice arrived. ## What a Reversal Actually Is Before tracking what happens to Mara, it is worth being precise about what has occurred. The term "chargeback" is used loosely — in practice it describes at least three distinct mechanisms, and which one has been triggered determines how much control Mara has over the outcome. A PayPal dispute is settled between buyer and seller, a claim is decided by PayPal, and a chargeback is decided by the card issuer. These are not interchangeable. The distinction matters enormously to anyone trying to respond effectively, because the decision-maker in each case is different, the evidence requirements are different, and the timeline is different. A chargeback is a transaction reversal initiated by the client's bank at the client's request — it was originally introduced as a consumer protection measure against fraudulent transactions. That original design was built around physical goods: a consumer orders something, it never arrives, the bank reverses the charge. Applied to professional services — work that has been scoped, delivered, revised, and explicitly accepted — the mechanism is a poor fit. But it applies regardless. A chargeback skips the platform completely. The buyer goes straight to their bank or card company — Visa, Mastercard, Amex — and asks them to reverse the charge. The card company decides, not the platform. This is the version Mara is dealing with. The client did not open a dispute on the platform. The client did not contact her. The client called their bank. ## The Timeline Mara Didn't Know About Buyers can file a chargeback up to approximately 180 days after purchase. Merchants get around 10 days to respond, and a card-issuer chargeback can take up to 75 days to resolve. Six weeks after final payment. Still within the window. Still entirely valid. Buyers can open a platform dispute up to 180 days after the original payment. If you do nothing within the dispute window, the case may escalate automatically, and you won't be able to reverse it. The 180-day window is not a quirk — it is policy, built into card network rules that no platform, no matter its terms of service, can override. Mara's client had every legal right to file the chargeback. Whether they had a reasonable basis for doing so is a separate question — one that the bank will not necessarily examine in depth. What Mara also did not know: sometimes clients file chargebacks when they feel they've received inadequate work; other times the freelancers haven't done anything wrong and the client is trying to get out of paying for the services they requested and received. The bank does not distinguish between these two motivations when the dispute arrives. It simply opens the case and waits for evidence. ## What the Platform Does First When the chargeback arrives, the platform's first move is not to defend Mara. A chargeback and any subsequent reversal instruction is made by the payment product issuer or third parties such as payment processors, not by the platform. The platform is bound to follow such instructions. This is the sentence buried in most platform terms of service that freelancers never read until they need it. The platform does not absorb the risk. The platform passes it on. The bank sends a chargeback to the platform, who then holds the disputed amount. For this reason, the order is canceled and the funds are taken from the freelancer's upcoming or cleared balance. The sequence is immediate and mechanical. No human reviews the situation before the funds move. The notification Mara received was not the beginning of a review process — it was confirmation that the funds had already left. The review, if there is one, comes afterward. After the chargeback has been reviewed, one of two scenarios will occur: either the freelancer is held responsible for service-related chargebacks and the funds are deducted, or the platform may protect the freelancer, under its sole discretion, from fraudulent chargebacks — though it is not guaranteed. "Sole discretion" is doing significant work in that sentence. It means Mara is not owed a defense. She may receive one. She may not. The decision belongs to the platform, and the criteria for that decision are not published in any detail. ## What Mara Can Do — and How Long She Has The freelancer gets notified and has an opportunity to contest the chargeback by providing evidence like contracts, communication records, and proof of work. The bank then reviews all the submitted information and the client's claim before making a decision. The response window is short. Customers have 120 days to file chargebacks; merchants have 20 days to respond to chargeback disputes. In some cases the window is tighter. Most card networks allow only 7 to 21 days to respond. Late submissions are automatically denied, even if you're right. Mara has roughly two to three weeks to assemble her case. What she needs is not a statement of events — it is documentation that matches the card network's specific evidentiary standard for service delivery. That means a signed contract referencing the exact scope delivered. It means a written record of the client's explicit acceptance of the final deliverable. It means timestamps on every submission. It means the revision history. It means the messages where the client said, in writing, that the work was complete and approved. She has some of this. She does not have all of it. The revision feedback was given over a video call. The acceptance of the final deck was verbal, followed by a payment release on the platform — which she assumed was sufficient. It was not. 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. Many banks and credit card companies view a signed contract as a piece of strong evidence when resolving chargeback disputes, making it a strong defence in any such situation. Mara's contract was a platform-generated agreement with the project title and the total amount. There was no scope breakdown. No defined deliverable list. No acceptance criteria. She submitted the strongest evidence she had — the final files, the revision messages she did have in writing, the platform's own confirmation that both milestones had been marked complete and paid — and filed her response within the window. ## The Wait Chargebacks take longer than most people expect — often 30 to 75 days. During that period, the funds remain held. Mara cannot access them. She cannot plan against them. They exist in a kind of administrative suspension, and her account balance reflects their absence. Once a dispute escalates, the platform becomes the liaison and the outcome will be determined by the uploaded evidence. They usually rule within 14 days, though sometimes it can take more than 30 days. For a freelancer with a healthy pipeline, a 30-to-75-day hold on several thousand dollars is uncomfortable. For a freelancer who allocated that money against expected expenses — rent, tax payments, subcontractors, software costs — it can cause downstream failures that have nothing to do with the original dispute. The psychological cost rarely appears in any analysis of chargebacks. But it is real and it compounds. Mara is not only managing a financial dispute — she is managing client relationships, incoming briefs, and her own reputation, all while waiting for a decision from an institution that has no relationship with her and no particular incentive to decide quickly. ## What It Costs The costs arrive in layers, and most of them are not recoverable regardless of outcome. The first is the disputed amount itself — the payment that was reversed at the moment the chargeback was filed. If Mara loses the dispute, that money is gone permanently. If the chargeback is approved, the funds are returned to the client, and the freelancer is often hit with a chargeback fee as well. Platforms are entitled to recover any chargebacks and reversals that may be imposed on them by a payment product issuer or third parties, as well as any processing or other fees whatsoever incurred on those chargebacks and reversals. That language — "any fees whatsoever" — is not an abstraction. It means the platform passes its own penalty costs directly to the freelancer. The second cost is time. Preparing a chargeback response is not a ten-minute exercise. Mara spent the better part of two days compiling documentation, drafting her rebuttal, reformatting communications into the submission format required by the platform, and coordinating with support. That is two days of unbillable work, absorbed entirely by her. The third cost is reputational, in the platform's own systems. Platforms actively monitor dispute rates — the ratio of claims and chargebacks compared to total transactions over the previous three months. If a dispute rate climbs to 1.5% or higher, the platform imposes additional fees per dispute. Beyond the fees, maintaining a high dispute ratio can trigger account limitations or even a permanent ban. Mara has never had a chargeback before. One incident will not end her account. But the rate has moved, and it will stay moved for three months regardless of the outcome of her specific dispute. The fourth cost — the one no one quotes — is the cost to her relationship with financial certainty. She will spend the next several weeks adjusting her financial planning around money she may or may not recover. She will think twice before withdrawing payment on future projects. She will carry a new, invisible overhead: the ongoing management of downside risk that she did not previously price into her day rate. ## What Winning Looks Like If Mara's evidence is sufficient and the bank rules in her favour, the funds are released back to her account. The chargeback fee may or may not be reimbursed, depending on platform policy and the specific ruling. The client's account on the platform is likely suspended — since chargebacks are against most platforms' terms of service, clients who reverse a payment will typically have their accounts suspended. The work is not returned. The client has it regardless of the outcome. The naming system, the positioning document, the manifesto — they exist in the client's files. What changes is only whether Mara gets paid for them. Winning a chargeback as a service provider requires something that the original transaction did not: forensic documentation that proves not only that the work was delivered, but that it met the agreed standard, that the client acknowledged it, and that the payment was authorised with full knowledge of what was being purchased. In other words, winning requires the professional infrastructure that most freelancers build only after losing once. ## What Losing Looks Like If the bank rules in the client's favour, Mara is out the full amount, plus fees. She has delivered the work. She cannot retrieve it. She has no automatic legal recourse — she can pursue the client in civil court, but that process is time-consuming, expensive, and typically impractical for project values under a certain threshold. The platform is not liable. The merchant bears the burden of proof. All the cardholder — the freelance client — has to do is contact the bank and ask for their money back. The asymmetry is structural. The client takes one action; the freelancer must build a case. A client who lost an internal platform dispute can still chargeback the transaction months after the fact. The platform's dispute process itself doesn't determine the chargeback outcome. Chargebacks can be filed to override it. This is the part that breaks most freelancers when they first encounter it. It means that even a resolved dispute, decided in the freelancer's favour by the platform's own team, can be overridden by the client simply picking up the phone and calling their bank. The platform's decision has no binding effect on the card issuer. ## The Structural Problem Mara's situation is not an edge case. It is a design feature of how payment works when a consumer-grade financial instrument — a credit card, a debit card, a digital wallet backed by a card network — is used to pay for professional B2B services. The chargeback mechanism was not designed for Mara's industry. It was designed for consumer retail. But it applies uniformly, and the burden it places on service providers — prove the work, prove the acceptance, prove the authorisation, prove it all within a tight window, prove it to an institution that has no context for your work — is a burden that was never factored into the price of doing business this way. Every freelancer operating through a platform that processes card payments is exposed to this risk on every single invoice. The payment clearing is not confirmation that the money is yours. It is confirmation that the process has moved to the next stage. Missing deadlines or submitting weak documentation often leads to automatic losses, fees, and higher dispute rates. The system is adversarial by default, and neutrality requires active preparation. ## After Mara Mara wins her dispute — narrowly, and six weeks after the chargeback was filed. The evidence she had was just enough. The platform's own milestone records, combined with the file submission timestamps and the written messages she did have, formed a case the bank accepted. Her funds are released. She pays a chargeback fee. She loses two days of client work. She rebuilds her financial projection for the quarter. She does three things differently after that. She builds a proper scope-and-acceptance protocol into every engagement: a document signed before work begins, a written acceptance email required at every milestone, and a record of every exchange related to deliverable quality kept outside the platform's messaging system. She moves to invoice directly where relationships allow, rather than routing everything through a single platform. And for multi-party projects — work that involves a client, a project budget, and third-party collaborators all in the same payment flow — she begins using Shaka, an onchain payment router that distributes funds the moment a transaction confirms, with no platform intermediary holding the money and no reversal mechanism once the smart contract executes. The reversal she experienced was possible because the money passed through a system designed to be reversible. Not every payment has to work that way. ## What to Actually Build The takeaway from Mara's situation is not that platforms are bad or that clients cannot be trusted. It is that the payment infrastructure freelancers rely on by default carries a risk profile that is rarely disclosed at the point of sale, is difficult to manage reactively, and can only be meaningfully reduced through proactive documentation and, where possible, payment architecture that settles finality at the moment of transfer rather than weeks after the fact. The documentation standard is not optional. A signed, scoped contract. A written acceptance at every milestone. Explicit written confirmation that deliverables met the agreed specification. All of it stored outside the platform, in formats that are exportable and submissible on short notice. The standard is not onerous — it is the same standard a consultant operating through a firm would apply automatically. Independent professionals need to apply it too, because the risk is the same and the institutional backing is not. The question to ask at the start of every engagement is not "what happens if the client doesn't pay?" — escrow-based platforms create a degree of protection against that. The question is "what happens if the client pays, and then reverses that payment after I've delivered?" That question has a different answer. And most freelancers only find out what it is when it's already happening to them.