If a fan claims they never got their order, check the order thread first: look for your own delivery timestamp before you reply. If delivery is confirmed there, share that record and offer to resend it. If it genuinely never sent, redeliver immediately or decline and refund the same day rather than argue back and forth by message.
FanBell is free to start with no monthly fee and applies a 12% platform fee only when a fan pays (pricing).
Most "I never got my order" messages are not accusations β they come from a fan who paid, expected something to show up somewhere obvious, and cannot find it. Stripe's dispute research names this the single most frequent non-fraud complaint merchants receive:
"'Product not received' disputesβwhere a cardholder claims they didn't receive what they paid forβare the most common nonfraud dispute category on Stripe."
β Stripe, Analyzing the evidence that helps businesses win "product not received" disputes (stripe.com)
That Stripe analysis was built from evidence packets in one million disputes collected over a 16-week period. Non-receipt claims are common because delivery confusion is common β not because most claims are bad faith.
What does "I never got my order" actually mean on FanBell?
On FanBell, "I never got my order" almost always means one of three things: the fan has not opened the delivery notification, the fan is looking somewhere other than the FanBell order thread, or the delivery genuinely failed. Every paid interaction lives in one timestamped order thread, so that thread decides which case applies.
Each FanBell order is tied to one specific offer β a Paid Private Question, a Personalized Shoutout, or a Creator Service. FanBell's own feature documentation states that "every question lives in a private thread in your creator inbox β not scattered across comments and DMs".
Be precise with the fan about where delivery appears: FanBell emails a notification containing a secure link when an order is delivered, and the reply, video, or file itself opens inside the FanBell order thread rather than arriving as an email attachment or a social DM (FanBell, how it works). A fan new to the platform can check an inbox, see no attachment, and conclude nothing was sent.
What should you check before you respond?
Before replying to a non-receipt message, open the order thread and confirm three things: whether your reply or file shows as sent, the delivery timestamp measured against the purchase time, and whether the format matches the offer β text for a Paid Private Question, video or files for a Shoutout or Service.
Checking the thread is usually quick, and it changes the entire response. A thread that clearly shows a delivered reply means a visibility problem, not a service failure. An empty thread means a real miss, where speed matters more than explanation. Never rely on memory β read the record before typing anything back.
Is "I never got it" different from "it wasn't what I expected"?
Yes, and the two need different responses. Non-receipt means nothing arrived at all. Dissatisfaction means something arrived but the fan does not think it matches what they paid for. Treating a quality complaint as a receipt problem, or the reverse, usually makes the conversation longer rather than shorter.
Card networks classify non-receipt and dissatisfaction separately too. Stripe maps Visa reason code 13.1, "Merchandise/Services Not Received," to its "product not received" dispute category, and maps Visa 13.3, "Not as Described or Defective Merchandise/Services," to a separate "product unacceptable" category (Stripe, dispute reason code categories). If the fan can describe what they received and simply does not like it, that is a scope question β see how to handle refunds for creator services for that path. This page covers only the case where the fan says nothing showed up.
How should you respond if the delivery is confirmed?
If the order thread shows a delivered reply or file, point the fan to the exact record instead of insisting it was sent. Name the delivery date and format, confirm which page the delivery opens on, and offer to resend it. Most fans accept a timestamp they can see for themselves.
Assume good faith on the first message: a fan who paid and cannot find what they bought is usually confused, not attempting a free order. For businesses selling physical goods, disputes that included delivery confirmation as evidence had a 27 percentage point higher win rate than disputes without it, according to Stripe's analysis of one million disputes. The same principle applies long before any dispute exists: show the record first. If the fan goes quiet after you point to the record instead of replying, see what to do when a fan stops responding after paying for how long to wait before acting further.
What evidence should you save on every order?
Save five fields for every paid order: the order ID, the purchase timestamp, the delivery timestamp, the delivered file or access link, and the full fan message history. On FanBell those five already sit in one order thread, so saving them means copying or screenshotting rather than reconstructing. The order ID and purchase timestamp also line up with what a fan sees on their own end β see whether fans get a receipt when they pay a creator for that side of the record.
| Evidence field | Where it lives on FanBell | Why it matters |
|---|---|---|
| Order ID | Order thread header | Ties your record to the exact Stripe charge under dispute |
| Purchase timestamp | Top of the order thread | Starts the clock the card network measures a dispute window against |
| Delivery timestamp | Your sent reply, video, or file in the thread | Proves delivery happened and when, the core of a non-receipt defense |
| Delivered file or access link | Attachment or reply in the thread | Shows what was delivered, not merely that something was sent |
| Fan message history | The same order thread | Documents scope agreed at purchase and any resend you offered |
| Refund record, if you refunded | Stripe dashboard for the charge | A full refund issued through Stripe was the strongest evidence predictor for digital goods in Stripe's study |
For digital deliverables, evidence that shows actual use outperforms evidence that shows dispatch. Disputes that included digital activity or usage logs β records showing a buyer streamed, downloaded, or accessed the specific product purchased β had a 10 percentage point higher win rate than disputes without them, and disputes with service documentation such as provisioning records had an eight percentage point higher win rate (Stripe). See what counts as evidence in a payment dispute for how to assemble these fields into a submission.
What if you actually never delivered it?
If the order thread shows nothing sent, treat the complaint as accurate and act the same day: apologize plainly, deliver now if you still can, or decline and refund the order. A miss handled within hours rarely becomes a dispute; a miss left for a week often does.
Turnaround is a commitment the creator made at purchase, not a vague expectation. FanBell's own documentation for Paid Private Questions states that the creator decides the price and how fast they reply, and its shoutout and service offers are configured with a price and a delivery window the creator sets (FanBell, Paid Private Questions and Personalized Shoutouts). A same-day fix or refund costs the creator the order value; an unresolved complaint that escalates costs the order value plus a dispute fee plus the time spent β the fan's side of this same scenario is covered in what happens when a creator doesn't deliver after being paid.
| Scenario | Likely cause | What to check | First action |
|---|---|---|---|
| Reply/file shows sent in the thread | Fan hasn't seen the notification | Timestamp vs. purchase time | Point to the record, offer to resend |
| Paid Private Question past its reply window | Reply genuinely missed | Order deadline vs. now | Reply immediately, or decline and refund |
| File/video attachment missing from thread | Upload didn't complete | Attachment field in the thread | Redeliver the same day |
| Fan checking email or social DMs instead | Confusion about where delivery lives | Confirm they're on the FanBell order page | Share the direct order link |
| Fan contacted their card issuer, not you | Escalated instead of messaging first | Stripe dispute notification | Gather evidence via Stripe's dispute flow |
What should you do if the fan doesn't accept your explanation?
If a fan still is not satisfied after seeing proof of delivery, refunding is often faster and cheaper than continuing to argue, especially on lower-priced orders. Holding your ground on a small purchase rarely returns more value than the hours it costs, and an unresolved complaint can escalate into a card dispute that carries its own non-refundable fee.
Stripe lists a dispute received fee of $15.00 for each dispute a US business receives, plus a further dispute countered fee of $15.00 for each dispute responded to manually (Stripe, Pricing & Fees). Fees differ by country, so a creator outside the US should check Stripe's pricing page for their own market (Stripe, how disputes work). Only one of those two fees comes back:
"Stripe returns the dispute countered fee if you win the dispute. Unless otherwise stated in your Stripe contract, we never return the dispute received fee."
β Stripe Documentation, How disputes work (docs.stripe.com)
Stripe documents two country exceptions: businesses in Mexico may have the received fee returned if they win or the cardholder withdraws, and businesses in the Single Euro Payments Area incur no received fee on card payments processed on the Cartes Bancaires network. None of that makes every complaint deserving of a refund β it is a judgment call about when arguing costs more than the order is worth. See how to protect yourself from chargebacks as a creator for how to weigh that trade-off earlier.
What happens if the fan files a formal dispute instead of messaging you?
A formal payment dispute is decided by the fan's card issuer, not by the creator or FanBell, on evidence submitted through Stripe. Card networks typically allow cardholders 120 days from the original payment to initiate a dispute, and the seller then usually has 7 to 21 days to respond (Stripe).
The timeline runs long past the response deadline. Stripe documents that an issuer reviewing submitted evidence usually takes 60 to 75 days to decide, and that the full dispute lifecycle from initiation to final decision can take 2 to 3 months. The same order-thread record used to answer a fan becomes the evidence packet β see what a chargeback is and how it affects creators for what the fee and outcome mean for your account.
One finding matters before refunding a fan who has already disputed: for businesses selling digital goods, disputes that included evidence of a full refund issued through Stripe had a 63 percentage point higher win rate than disputes without it, while refunds issued through other channels such as store credit produced only a six percentage point lift. Refund through the original payment path, and keep the record.
How do you avoid "never got it" disputes in the first place?
The strongest defense against a non-receipt claim is a habit rather than a reaction: keep every request, revision, and delivery inside the FanBell order thread, and route no part of an order through outside DMs or email where no shared timestamped record exists.
Setting an honest turnaround helps as much as the record does, because many non-receipt complaints start as impatience rather than accusation. See proof of delivery for personalized creator services for what to save on every order, and how to protect yourself from chargebacks as a creator for the broader prevention checklist.
Frequently asked questions
What's the first thing I should do when a fan says they never got their order?
Open the order thread and check whether your reply or file shows as delivered, then compare that delivery timestamp to the purchase time, before responding to the fan. That single check tells you whether you are dealing with a visibility problem or a genuine missed delivery.
Should I assume the fan is lying?
No. Stripe reports that "product not received" is the most common nonfraud dispute category on its platform, which means most such claims come from genuine confusion about where a delivery lives rather than deception. Start from the assumption that the fan cannot find what they paid for.
What if I can't tell whether I delivered it or not?
If your own order thread does not clearly show a delivered reply or file, treat the order as undelivered: apologize, deliver now if you still can, or decline and refund the order the same day rather than leaving it unresolved.
What evidence should I keep for a "never got it" claim?
Keep the order ID, the purchase timestamp, the delivery timestamp, the delivered file or access link, and the full fan message history β all five sit in the FanBell order thread. For digital goods, Stripe found that usage or access logs raised dispute win rates by 10 percentage points versus disputes without them.
Does refunding a "never got it" claim always make sense?
Not always, but refunding is frequently the lower-cost outcome once proof of delivery has been shown and the fan still is not satisfied, particularly on lower-priced orders. Weigh the refund against the time spent plus Stripe's $15.00 dispute received fee for US businesses, which is not returned even when the seller wins.
What if the fan skips messaging me and disputes the charge with their bank?
That is a formal dispute decided by the card issuer on evidence submitted through Stripe, with a seller response window of usually 7 to 21 days depending on the card network. See what counts as evidence in a payment dispute for what to gather and submit.
Keep reading
Ready to get paid for the interactions you already get?
Create your free FanBell link