Proof of Delivery for Personalized Creator Services

Proof of delivery is a timestamped record showing what a fan requested and what you sent back: the in-platform thread, the delivered file or message, and the date it was sent. Saving this as a habit — not scrambling for it after a complaint — is what makes a later dispute or chargeback response fast instead of stressful.

FanBell is free to start with no monthly fee and applies a 12% platform fee only when a fan pays (pricing).

Most creators never need this record. But card-network disputes exist, and card issuers side with the person who can show what happened, not the person who is more upset about it. Stripe states that "fraudulent disputes account for over half of all disputes" (Stripe, Dispute evidence best practices), so a delivery record is often the only thing separating a real complaint from a cardholder who simply did not recognize a charge. Stripe's published US standard pricing charges a dispute received fee of $15.00 for each dispute a business receives (Stripe pricing), which means even a dispute you eventually win has a cost attached.

Stripe's own guidance to sellers is direct: "if your business provides digital goods, include evidence such as an IP address or system log proving the customer downloaded the content or used your software or service". For a creator selling a custom video, a written answer, or a scoped review, the equivalent is the delivery record itself: the request, the reply, and the timestamp connecting them.

What counts as proof of delivery on FanBell?

On FanBell, proof of delivery is the order thread itself: the fan's original paid request, your completed reply, and the timestamps on both, stored against that one order. No separate delivery-confirmation tool is needed, because every paid interaction on FanBell already runs through a private, dated thread (how it works).

The thread that already exists for Creator Services, Personalized Shoutouts, and Paid Private Questions is the record. What changes by offer is what the thread can hold: a Paid Private Question thread carries text from the fan and a text or voice reply from the creator, with no file uploads in either direction, while a Service or Shoutout thread can hold files, links, audio, and video (Paid Private Questions and Creator Services). For creators choosing an offer before worrying about delivery records, lower-effort creator products and services are often simpler than building a course.

Why keep delivery proof before a dispute happens?

Keep delivery proof before a dispute happens because the response clock is short: Stripe tells sellers they usually have 7 to 21 days to respond, depending on the card network (Stripe, Respond to disputes). Reconstructing a delivery from memory after a complaint rarely fits inside that window.

Missing the 7-to-21-day dispute response deadline is not a partial loss. Stripe states that "if you don't respond before the deadline, you automatically lose the dispute and can't retrieve the disputed funds". Treating the in-thread record as the delivery file, rather than something to recreate later, means a creator never starts a response from zero.

Pre-dispute warning signs also convert at a high rate: Stripe reports that unless a payment is covered by the liability shift rule, 80% of early fraud warnings turn into a fraud dispute if the business does nothing.

Dispute volume carries a cost beyond any single refunded order. Stripe writes that the credit card processing industry standard recognizes dispute activity above 0.75% of payments as excessive (Stripe, Measuring disputes). Stripe's dispute guide puts the network fines that follow entry into a card-network monitoring program at $50 to $150 per dispute (Stripe, Introduction to payment disputes), so an unanswered delivery complaint can cost a creator more than the order was worth.

What proof exists for Creator Services and Shoutouts?

For a Creator Service or Personalized Shoutout, proof of delivery is the file, link, or video sent inside the order thread, plus its timestamp. Both offers support full media in both directions, so the fan's request, any files they attached, and the delivered reply sit in one dated record.

Practical habits worth adding on top of the built-in thread:

• Keep a local backup of large video or audio files for at least 120 days after delivery, matching the outer window in which card networks typically allow a cardholder to open a dispute (Stripe).
• If a request has a specific, describable scope (for example, "one 60-second birthday video for my dad"), that description matching the delivered file is itself part of the proof — it shows what was ordered and what was sent.
• Note the delivery date against FanBell's turnaround cap. FanBell caps a Service or Shoutout delivery promise at 120 hours, or 5 days, and a creator sets any turnaround between 1 and 120 hours, so a timestamped reply inside that window shows the delivery was on time.

What proof exists for Paid Private Questions?

For a Paid Private Question, proof of delivery is the reply itself, because no file ever changes hands. FanBell's Paid Private Questions are text-only from the fan, and the creator answers in the same private thread by text or recorded voice, never by file or video upload.

The text-only format does some of the delivery-proof work for a creator: with no file exchange in either direction, the question "was anything actually delivered" resolves by reopening the FanBell order thread. Reply time is the only turnaround a creator sets on a Paid Private Question. FanBell fixes the rest of the exchange as a platform rule rather than a creator setting: one paid question plus up to two follow-ups, with the fan's follow-up window closing 24 hours after the creator's first reply.

How long should you keep proof of delivery?

Keep delivery records for at least 120 days after payment. Stripe states that card networks typically allow cardholders to initiate disputes within 120 days of the original payment, while noting that network rules allow more time in some situations.

Visa's own consumer guidance sets the same outer window for cardholders in the UK.

"You usually have up to 120 days after the purchase to make a chargeback claim, but you should not start a claim unless you have tried to get a refund directly from the seller." — Visa, Chargeback and purchase disputes

Pre-dispute inquiries follow a similar clock: Stripe closes an inquiry that has stayed open for 120 days without escalating to a chargeback, after which the card network will not escalate it.

US credit-card law sets a separate and shorter clock than the card networks do. Under Regulation Z, a cardholder's billing-error notice must reach the card issuer "no later than 60 days after the creditor transmitted the first periodic statement that reflects the alleged billing error" (CFPB, Regulation Z § 1026.13(b)(1)). The 60-day statutory notice window applies to US cardholders and runs alongside the card networks' 120-day dispute window, so a creator retaining files should plan against the longer 120-day figure.

The 120-day dispute window is far longer than the window a seller gets to submit evidence. A creator therefore has two different retention clocks: 120 days for "could this payment still be disputed," and 7 to 21 days to assemble and submit a response once a dispute lands (Stripe). The FanBell thread persists as the order record, so the only extra habit is keeping local copies of large delivered files for those 120 days.

What happens if a fan disputes the card charge?

If a fan disputes the card charge, the fan's bank decides the outcome, not FanBell and not Stripe. Mastercard states that for a merchant contesting a chargeback, "the deadline is typically 20 to 45 days after the merchant is notified" (Mastercard), while a payment processor may require the evidence sooner.

Stripe is explicit that it does not decide the result: Stripe "facilitates your case, but doesn't have influence over the outcome, which is at the sole discretion of the account owner's bank". Stripe also debits the disputed amount plus the dispute fee from the seller's balance as soon as the dispute is created, so funds move before any evidence is reviewed.

Even strong evidence does not guarantee a win. Stripe's Radar win-likelihood prediction tops out at a 60% expected chance of winning for the strongest 5-dot disputes and falls to 5% for 1-dot disputes, and Stripe writes that "even in the most favorable cases, it's very difficult to overturn a disputed payment". Stripe's 60% top-end number is a predicted win rate for the best-documented disputes, not a guarantee, so proof of delivery improves a creator's odds without settling the outcome. Stripe adds that Visa is the only card network with a formal Compelling Evidence specification, and that a business which submits no Compelling Evidence has a "very low" likelihood of overturning a Visa fraud dispute.

Visa's Compelling Evidence 3.0 route is also closed to most one-off creator orders. Stripe documents that a Visa CE 3.0 response requires at least 2 previous transactions from the same cardholder that were not disputed and that used the same payment method, each dated 120 to 364 days before the disputed transaction (Stripe, Visa Compelling Evidence 3.0 disputes). A first-time fan buying a single Shoutout therefore leaves a creator with the ordinary evidence route: the request, the delivered reply, and the timestamps on both.

Where do fan claims get raised on FanBell first?

On FanBell, an "I didn't get what I paid for" claim usually arrives first as a message in the order thread, long before any card dispute exists. The fastest response is to reopen that thread and point to the timestamped delivery inside it, because FanBell stores the fan's request and the creator's reply together.

The delivery-side remedy built into the product is decline-and-refund: FanBell's own documentation tells creators, "you can decline and refund it," for any request a creator cannot or does not want to fulfil. FanBell does not adjudicate whether a delivery happened; once a claim becomes a formal card dispute, the decision sits with the cardholder's bank, which Stripe describes as having "sole discretion" over the outcome. The FanBell thread record and the decline-and-refund option are the only tools available before a card dispute is filed. When a pre-dispute fraud warning does arrive, Stripe advises that refunding is likely not worthwhile on charges more than 35 percent higher than the business's dispute fee.

What's the difference between platform proof and dispute evidence?

Platform proof is the record sitting in a FanBell order thread: the request, the reply, and the timestamps. Dispute evidence is that same material reorganized into the format a card issuer expects and submitted through Stripe inside the 7-to-21-day response window. Platform proof is storage; dispute evidence is a submission built from it.

Submitting has its own price. Stripe's US standard pricing lists a dispute countered fee of $15.00 for each dispute a business responds to manually, refunded on won disputes and kept on lost ones, on top of the $15.00 dispute received fee. Stripe also recommends organizing evidence chronologically and grouping receipts, communications, policies, and system logs into separate sections.

"Card issuers review thousands of dispute responses every day. Writing a long explanation to them isn't going to make your responses more convincing." — Stripe, Dispute evidence best practices

The practical takeaway is that a delivery habit should stay simple. Keep the request and reply together, dated, in the thread they already live in, and organize a longer response only if a formal dispute actually arrives. Related reading: how to protect yourself from chargebacks as a creator covers the broader prevention checklist, how payment disputes are resolved for digital services walks through the formal process end to end, and creators selling to fans abroad may also want how VAT applies to digital services sold to EU fans.

Frequently asked questions

Do I need to screenshot every delivery just in case?

Not necessarily. The FanBell order thread already keeps the request and the reply together with timestamps, so for most creators that is the record. Screenshotting is worth adding for large video or audio files you might delete locally, or if you want a backup outside the thread.

What if a fan says they never got a Personalized Shoutout after it was delivered?

Reopen the order thread — the delivered video and its timestamp are the proof of delivery. If the fan's device or notifications failed to alert them, resending the same delivered file through the thread is usually the fastest resolution before anything becomes a formal dispute, which Stripe says card networks typically allow a cardholder to open within 120 days of payment.

Is a text reply to a Paid Private Question enough proof on its own?

Yes. FanBell's Paid Private Questions are text-only from the fan, with a text or voice reply from the creator and no file uploads in either direction, so the thread itself is the complete delivery record.

How is this different from a formal chargeback dispute?

A chargeback is a separate process handled by the fan's card issuer, with its own evidence format and a response window Stripe puts at usually 7 to 21 days depending on the card network. The delivery record in a FanBell thread is the raw material for that response, not the response itself. See how payment disputes are resolved for digital services for the full process.

Does FanBell charge extra for handling a dispute?

No. FanBell is free to start with no monthly fee and a 12% platform fee only when a fan pays. Card processing is billed separately by Stripe, whose US standard pricing is 2.9% + 30¢ per successful domestic card transaction and adds a dispute received fee of $15.00 per dispute plus a $15.00 dispute countered fee for each dispute answered manually, refunded if the dispute is won; rates outside the US vary by country.

Create your free FanBell page