# When you are the merchant of record, the chargeback is yours Keeping the whole price means your name is on the buyer's statement — and you are the one who answers when they dispute it. What a chargeback on a $9.99 ebook actually costs, and the four things that stop most of them being filed. - Published: 2026-09-03 - Last updated: 2026-09-03 - Author: Inkwharf - Canonical: https://www.inkwharf.com/blog/the-chargeback-is-yours-now - Publisher: Inkwharf — https://www.inkwharf.com/llms.txt ## Takeaways - On a direct sale you are the merchant of record — the disputed amount and the dispute fee both come out of your balance, not a platform's. - A $9.99 book lost to a chargeback costs about $25 once the ~$15 fee is counted. The rate is low; the unit cost is not. - Most disputes are "I don't recognise this charge," and a clear statement descriptor plus an instant receipt prevents them. - A watermarked file and a working recovery page are what win the disputes that do get filed. --- Every comparison of selling direct against selling through a retailer quotes one number back at you: the percentage. Keep about 94% instead of 70%, keep 100% on bitcoin. What that comparison leaves out is the sentence underneath the number — *you are the merchant of record* — and one of the things that sentence means is that chargebacks are now a line item in your business. This is not a reason to sell through a retailer. It is a reason to set up the four things that make it a rounding error instead of a recurring surprise. ## The trade nobody quotes back to you When a retailer sells your book, they are the merchant. Their name is on the card statement, their account eats the chargeback, their team argues with the bank. You never see it — it is folded into the 30% before you get paid. When you sell direct, the charge is created on your own payment account. That is what keeps the whole price in your hands. It also means the buyer's statement says something derived from *your* account, the dispute lands in *your* dashboard, and the fee comes out of *your* balance. Nobody is standing between you and the money, [in either direction](/blog/sell-ebooks-from-your-own-website) — that phrase is doing real work here. ## What a chargeback costs, concretely Three things leave at once: - **The sale.** The $9.99 is pulled back from your balance. - **The fee.** The card network charges the merchant a dispute fee regardless of who wins — around $15 with most processors, and it is not refunded even if you prove the charge was legitimate. - **The time.** Assembling evidence and submitting a response is fifteen to thirty minutes you did not plan to spend. So a disputed $9.99 sale is roughly a **$25 event**, not a $10 one. The saving grace is volume: dispute rates on legitimate digital-goods businesses sit well under 1% of transactions, and a bookshop selling to its own newsletter is at the calm end of that. A handful a year, at $25 each, against a percentage cut on every single sale for life — the arithmetic still points the same way. But $25 is the right number to have in your head, not $10. ## Why they happen Four causes, in roughly the order they occur: 1. **"I don't recognise this charge."** The statement shows an unfamiliar name weeks after a one-time purchase the buyer forgot about. This is the majority of disputes and the most preventable. 2. **Buyer's remorse dressed as a dispute.** The reader wanted a refund, could not immediately see how to ask, and hit the button their bank made easy instead. 3. **Friendly fraud.** The buyer has the book and disputes the charge anyway. Rare at this price — the effort-to-reward ratio is bad for them — but not zero. 4. **Genuine delivery failure.** The download link broke, the email went to spam, the reader gave up. This one is your fault and worth finding out about before it becomes a dispute. ## The four things that prevent most of them **A statement descriptor with your shop's name in it.** This is a setting in your payment provider, it takes two minutes, and it defuses cause one entirely. The buyer should see the same name on their statement that they saw at checkout. **An instant, itemised receipt.** Emailed the second the payment clears, with the book title, the price, the date, and a reply address that reaches you. A reader holding a receipt does not call their bank; they reply to the receipt. **A refund path a reader can find in ten seconds.** The [refunds page](/legal/refunds) should say who to contact and how, and the confirmation email should link to it. Every refund you grant quickly is a chargeback you did not get — and a refund costs you the sale but not the $15 fee. **A recovery page that works.** The reader who lost the download email is a dispute in waiting. A page where they enter the address they paid with and get fresh links for every purchase turns that reader back into a happy one. This is the [eighteen-months-later problem](/blog/sell-ebooks-from-your-own-website), and it is the same fix. > **The verdict:** you cannot make chargebacks impossible, and trying to is a > waste of a good afternoon. You can make the honest 95% never happen — a name > on the statement, a receipt in the inbox, a refund one reply away — and eat > the rest as a cost of keeping the whole price. ## The disputes you will lose If a buyer files a dispute for "product not received" and you sold a DRM-free file with no account required, your evidence is thin: you cannot show a login, a stream, or a device activation. A [watermarked copy](/blog/you-are-renting-your-library) helps — it ties the delivered file to that purchase — and delivery logs help, but banks weight these toward the cardholder and you will lose some. At $25 a loss and a rate this low, that is a subscription you are not paying to a fraud-management department. It is fine. ## Bitcoin: no chargebacks, a different trade A bitcoin payment cannot be reversed by anyone — not the buyer, not their bank, not you. There is no dispute mechanism because there is no intermediary to appeal to. That removes the chargeback problem completely and replaces it with a support problem: a refund is a fresh payment you send by hand, at a bitcoin price that has moved since the sale. [What paying in bitcoin actually does](/blog/what-happens-when-you-pay-in-bitcoin) walks through both sides. Most readers will still pay by card, which is why the card path is the one worth getting right first. ## Where this platform sits Inkwharf takes [nothing per sale](/data/ebook-platform-fees) on either rail, which is the same fact that makes chargebacks yours: no money passes through here, so there is no balance to absorb a dispute from and no team to argue one on your behalf. What you get instead is the checkout built to prevent them — your descriptor, an instant receipt, a linked refund policy, and a recovery page every buyer can reach — so the four things above are defaults rather than a setup checklist. The [take-rate calculator](/tools/take-rate) puts the fee picture against a retailer's cut on your own numbers. **[Open a shop](/register?role=author)** — your own payment account, your name on the statement, and the dispute-prevention plumbing already wired in.