How to Protect Yourself From Chargebacks as a Creator

Protect yourself from chargebacks by making the delivery obvious to prove: agree on price and scope before payment, keep every request and response inside one written thread, save proof of what and when you delivered, and reply quickly if a fan follows up. None of this guarantees a win, but it removes the ambiguity that chargebacks depend on.

A chargeback starts with the fan's bank, not with the creator, and by the time the creator hears about it the money has already left the balance. Stripe withholds the disputed amount and the applicable dispute fee from a merchant's balance as soon as a dispute is opened (Stripe: disputes). The only real defense is a clear record — a thread, a delivery timestamp, a written scope — that supports what actually happened.

The 7-step chargeback prevention checklist

Chargeback prevention for a creator is seven repeatable steps applied to every paid request: write the scope before payment, use a recognizable checkout, keep one thread, deliver inside that thread, timestamp the delivery, answer follow-ups fast, and refund proactively when an order cannot be filled. Contesting a dispute afterwards is the weaker fallback.

1. Write the scope before the fan pays. State the price, the deliverable, the revision limit, and the turnaround in text the fan can read and agree to.
2. Sell through one checkout with a recognizable statement descriptor. Stripe lists transaction clarification alongside proactive customer service as ways to avoid a dispute entirely.
3. Keep the whole conversation in one thread. Scattered DMs across three apps cannot be assembled into a chronological record on a deadline.
4. Deliver inside that same thread, not by a separate channel. The delivery and the original request should sit next to each other.
5. Timestamp what was sent. Save the dated message, the uploaded file, or the delivered link at the moment of delivery.
6. Answer every follow-up message quickly, even a partial answer. Stripe advises businesses to "always respond to inquiries immediately, making every effort to amicably resolve issues with your customer during this stage" (Stripe: how disputes work).
7. Refund proactively when a request cannot be delivered, and keep the evidence submittable. Stripe accepts only PDF, JPEG, or PNG dispute evidence, capped at 4.5 MB combined and fewer than 50 pages, with a 19-page limit on Mastercard (Stripe: dispute evidence best practices).

What is a chargeback, and how does it differ from a refund?

A chargeback is a forced payment reversal that a fan's card issuer initiates with the bank, pulling money out of a creator's balance before the creator is consulted. A refund is a reversal the creator chooses to issue. The difference that matters is cost: a refund returns only the payment, while a chargeback adds a fee.

Stripe defines a dispute as occurring when "an account owner contacts their bank to contest a payment to you," a different process from a fan simply sending the creator a message (Stripe: how disputes work). Stripe's published fee details by country list a 15 USD dispute received fee and a 15 USD dispute countered fee for United States businesses (Stripe: fee details by country). Stripe's disputes documentation is explicit about which of those two fees comes back: "Unless otherwise stated in your Stripe contract, we never return the dispute received fee" (Stripe: how disputes work — dispute fees). That fee asymmetry — a received fee that never comes back, and a countered fee that returns only on a win — is why answering a fan directly, before the fan thinks to call the bank, is almost always the cheaper path.

Why are creators especially exposed to chargeback risk?

Creators are exposed to chargeback risk because personalized digital work leaves no tracking number and no physical object to point at, so the only evidence that anything was delivered is whatever the creator chose to save at the time. A long filing window widens that gap: a fan can dispute a charge months after the work was sent.

Stripe states that "card networks typically allow cardholders to initiate disputes within 120 days of the original payment, but their rules allow more time in some situations" (Stripe: how disputes work — dispute timing). Stripe's dispute evidence guidance also reports that fraudulent disputes account for over half of all disputes, so most disputes are not arguments about quality at all (Stripe: dispute evidence best practices).

The 120-day filing window is long enough for a fan to forget a small charge or fail to recognize the statement descriptor next to it (Stripe: measuring disputes). Unclear scope compounds the problem: a fan who expected a full rewrite but received a redline may not think "I got what I paid for" — that fan may think "I didn't get what I ordered," which is exactly the framing that produces a bank dispute instead of a message to the creator.

How does clear scope prevent a chargeback before it starts?

Clear scope prevents chargebacks by closing the gap between what a fan expected and what arrived. Write down the price, the deliverable, the revision limit, and the turnaround before the fan pays, so any later complaint has a written reference point instead of two conflicting memories of the same conversation.

Scope also changes which dispute rules apply. The US Federal Trade Commission states that credit card billing errors include charges "for items that you didn't accept or that weren't delivered as agreed," while "disputes about the quality of the item are not billing errors" (FTC: billed for things you never got). A written scope is what moves a complaint from "never delivered as agreed" toward "delivered, but I wanted more," which is a much weaker basis for a formal billing-error dispute.

A Creator Service or Personalized Shoutout listing that states price, deliverable, and turnaround up front gives the creator something concrete to cite later. A formal signed contract is usually unnecessary for a one-off service, but at least two US states now set a dollar threshold above which a written contract is required by law. The Illinois Freelance Worker Protection Act requires a written contract when "the value of that work is equal to or greater than $500 in a 120-day period," for contracts taking effect after July 1, 2024. California's Freelance Worker Protection Act sets its threshold at "an amount equal to or greater than two hundred and fifty dollars ($250)," counted across all contracts between the same two parties in the preceding 120 days. Both statutes are state-specific and cover professional services, so a creator outside Illinois and California should check local law rather than assume a written scope statement is legally sufficient (do you need a contract to sell personalized creator services). FanBell's purchase and refund policy sets the platform-wide baseline, and a creator's own listing can add specifics on top of that baseline.

What proof of delivery should you keep for every paid request?

Keep a timestamped record of exactly what was sent and when, stored in the same thread where the fan made the request: a screenshot of the file upload, a saved copy of the delivered video, or a dated message. Proof captured at the moment of delivery is far stronger than a timeline reconstructed weeks later.

Delivery time on FanBell Creator Services and Shoutouts is capped at up to 120 hours, so tying the delivered file, link, or message to the original request thread keeps the timeline easy to reconstruct (how it works). If a formal dispute is opened with a card issuer, Stripe gives the merchant a limited window to respond — usually 7 to 21 days, depending on the card network — before the evidence deadline passes (Stripe: how disputes work). Evidence gathered after the response window closes generally cannot be submitted at all.

Replying fast to a follow-up message matters as much as saving the file. Stripe presents a reply as a way to stop a dispute before it is ever filed, writing that "you might avoid a dispute entirely with proactive customer service and transaction clarification" (Stripe: how disputes work). Treat fast replies as operational advice rather than a measured effect: no public data set separates fans who received an acknowledgment from fans who heard nothing. If a creator genuinely cannot deliver, declining and refunding the request beats leaving it unanswered (how to handle refunds for creator services).

What should you do before a dispute happens, not after?

Build one documentation habit and apply it to every paid request, before any single order becomes a problem: agree scope in writing, deliver in-thread, save the timestamp, and answer follow-ups quickly. A consistent routine protects a creator far better than a scramble assembled after a fan is already upset and already on the phone with a bank.

Acting early is measurable in one narrow case: Stripe reports that 80% of early fraud warnings convert into a fraud dispute if the business does nothing (Stripe: how disputes work — early fraud warnings).

A fan also has genuine legal footing to dispute a charge, not just a platform courtesy. Under the US Fair Credit Billing Act, a cardholder must dispute a billing error in writing within 60 days of the statement that shows the charge, and the issuer must acknowledge the dispute in writing within 30 days and resolve it within two billing cycles, but no more than 90 days (FTC).

"By law, credit card billing errors must be disputed in writing within 60 days of the date that the first statement with the billing error is sent to you." — US Federal Trade Commission, What to do if you're billed for things you never got

The Fair Credit Billing Act protects US cardholders specifically. A fan paying from outside the US disputes under that country's own consumer rules and the card network's timelines instead, so the 60-day figure should not be treated as a worldwide deadline. Either way, the practical response is the same: make the creator's side of the story easy to verify rather than treating every dispute as bad faith.

What does a lost chargeback actually cost a creator?

A lost chargeback costs the disputed amount plus fees, and the money leaves the balance before the outcome is known. Stripe deducts the disputed payment and the dispute fee as soon as the dispute opens, and the fee charged for receiving a dispute is not returned regardless of how the case is eventually decided.

Stripe's fee details by country list a 15 USD dispute received fee and a 15 USD dispute countered fee for United States businesses, and a 20 GBP dispute received fee with a 20 GBP dispute countered fee for United Kingdom businesses (Stripe: fee details by country). Stripe describes the countered fee as one that "will only apply when you counter a dispute and will be returned to you if you win" (Stripe: fee details by country), while the disputes documentation states that "unless otherwise stated in your Stripe contract, we never return the dispute received fee". Fee terminology and refundability vary by country: Stripe notes that the dispute countered fee does not apply to businesses in Mexico or Japan, that businesses in Mexico may have the dispute received fee returned if they win, and that SEPA businesses incur no dispute received fee on Cartes Bancaires card payments (Stripe: how disputes work — dispute fees). Card processing is billed separately at 2.9% + $0.30, the typical US domestic online-card rate on Stripe's standard pricing (Stripe pricing).

"After a chargeback is created, you have a limited time to respond to the card issuer: usually 7-21 days, depending on the card network. If you submit evidence, the issuer has a limited time to evaluate it and decide the outcome: usually 60-75 days, depending on the card network." — Stripe, How disputes work

The merchant response window and the issuer evaluation window together mean a full dispute can run roughly two to three months from the moment a fan files it to the final decision. Contesting is also not a coin flip: Stripe's Radar dispute win-likelihood ranking puts the highest score, five dots, at a 60% chance of winning and the lowest, one dot, at 5%, and Stripe adds that "even in the most favorable cases, it's very difficult to overturn a disputed payment" (Stripe: dispute evidence best practices). There is no FanBell-run appeals process layered on top of the card network's review: the evidence submitted through Stripe's response window is the mechanism, alongside declining and refunding requests that cannot be delivered.

How many chargebacks trigger card-network monitoring?

Card-network monitoring starts at published dispute-rate thresholds rather than at a vague sense of "too many." Stripe's documentation states that the credit card processing industry standard recognizes dispute activity above 0.75% as excessive, and that a sudden spike or steep upward trend can trigger placement into a monitoring program even below that threshold (Stripe: measuring disputes).

The specific network thresholds are higher than 0.75%. The Visa Acquirer Monitoring Program's non-compliant threshold is a 0.5% VAMP ratio with a count of 5, and its excessive threshold is a 1.5% ratio with 1,500 disputes and fraud reports in the US, EU, Canada, AP, and LAC regions (Stripe: dispute and fraud card monitoring programs). Mastercard's Excessive Chargeback Merchant level starts at 100 to 299 chargebacks in a month combined with a chargeback rate of 1.5% to 2.99% (Stripe: dispute and fraud card monitoring programs).

Most individual creators sell nowhere near the volume those counts require, so monitoring programs are unlikely to be the practical risk. Two facts still matter for any creator: Stripe notes that monitoring programs do not consider dispute outcomes, so won disputes count the same as lost ones, and refunds issued before a dispute is raised do not count at all (Stripe: dispute and fraud card monitoring programs).

How does FanBell reduce chargeback risk for creators?

FanBell reduces chargeback risk by keeping the request, the agreed terms, the replies, and the delivery inside one order thread, so the documentation a dispute needs already exists rather than being assembled under deadline. FanBell is free to start with no monthly fee and applies a 12% platform fee only when a fan pays (pricing).

Paid Private Questions are text-based with a fixed reply window. Creator Services and Personalized Shoutouts carry a set price, a stated turnaround, and a delivered file, link, or video, all timestamped inside the same order.

Structure does not replace judgment: a creator who ignores a follow-up or ships work outside the agreed scope can still face a dispute. Keeping the request, the terms, and the delivery in one place does not remove chargeback risk, and no public data set measures how much it lowers that risk. What one thread does produce is the evidence Stripe names as standard in a dispute response: customer communication, a receipt, and "a description of the product or service and any relevant details on how this was presented to the customer at the time of purchase" (Stripe: dispute evidence best practices).

Frequently asked questions

Does saving proof of delivery guarantee I'll win a dispute?

No. Winning a formal card-network dispute depends on the issuing bank's review of the evidence submitted inside Stripe's response window, and outcomes are not guaranteed either way. Saved proof and a clear scope statement make the creator's case easier to present, but the final decision belongs to the fan's card issuer, not to the creator or to FanBell.

Can I avoid the Stripe dispute fee if I win?

Partly. Stripe returns the 15 USD dispute countered fee to United States businesses that win, but never returns the separate 15 USD dispute received fee, which is charged on every dispute received (Stripe: fee details by country). Resolving an issue with a fan before the fan escalates to a bank is the only way to avoid both fees.

Do the dollar figures apply if I'm not in the US?

No. Stripe sets dispute fees per country: its fee details list 15 USD for a dispute received in the United States and 20 GBP for the same event in the United Kingdom, and the dispute countered fee does not apply at all to businesses in Mexico or Japan (Stripe: fee details by country). The Fair Credit Billing Act's 60-day written-dispute deadline is also US-specific, so creators outside the US should check their local Stripe pricing page and local consumer rules.

Is a refund always cheaper than risking a chargeback?

Usually, but not always. A refund issued by the creator avoids the 15 USD dispute received fee entirely, since that fee is only debited once a fan's bank formally opens a dispute (Stripe: fee details by country). Stripe also notes that monitoring programs do not count refunds as disputes, which is another reason a proactive refund is usually the lower-cost outcome for an order that cannot be delivered.

Do I need a signed contract to protect myself from chargebacks?

Not usually, but state law can require one. A clear written scope — price, deliverable, revision limit, turnaround — agreed to before the fan pays covers most day-to-day disputes. Illinois requires a written contract when freelance work is worth $500 or more in a 120-day period, and California requires one at $250 or more aggregated over the preceding 120 days. Creators elsewhere should check local law.

What does FanBell charge on top of Stripe's fees?

FanBell is free to start with no monthly fee and applies a 12% platform fee only when a fan pays. Stripe's card processing is separate, at the typical US domestic online-card rate of 2.9% + $0.30, plus a 15 USD dispute received fee if a fan formally disputes a charge with a bank (Stripe: fee details by country).

Create your free FanBell page and keep every paid request, reply, and delivery in one documented thread from the start.