To sell EPUB ebooks directly, give the buyer both a paid download and a clear route into their reading app. A successful payment does not mean the book has reached the reader's library. Treat checkout, file download and reader import as three separate steps, with support instructions for each.
This article is for independent authors who already have a finished book and an audience. The original handoff card below connects PayRequest's download behavior to the reader's next action. It is a proposed release protocol, not a claim that we tested your manuscript or every reading device.
Choose the File the Reader Will Actually Use
Offer a reflowable EPUB for a primarily text-based book when readers need adjustable text. A PDF can be a useful companion for a worksheet or fixed-layout reference, but label it separately. Do not promise that a PDF and EPUB will display identically.
Publish the formats, language, edition and any device limitations before checkout. If the product is a ZIP containing an EPUB and extras, explain that buyers must extract it first. A directly downloadable EPUB removes that extra step for a single-book offer.
PayRequest's current upload implementation accepts EPUB, PDF and ZIP. It delivers the file; it does not convert the manuscript, install a reading app or automatically add the book to an Amazon library. The ebook product page is the starting point for this offer. For the provider-specific setup, see selling ebooks with PayPal.
Validate an EPUB Before Selling It Directly
Run the exact retail file through EPUBCheck, the W3C project's EPUB conformance checker. Resolve errors and review warnings. A passing result checks conformance; it does not prove that navigation, image descriptions or reading order are useful to a human reader.
Open the same file in the apps you intend to support. Increase the font size, follow the contents navigation, move between chapters and test footnote return links. Look for clipped diagrams and missing characters. Record the app, operating system and date instead of advertising universal compatibility.
Keep a release record with book title, edition, filename, checksum and validation result. A corrected chapter should produce an identifiable new file so support can tell which edition the buyer opened.
Copy This Download-to-Reader Handoff Card
Use one row per promised reader path. The sample entries describe what to test, not completed tests.
| Stage | Buyer action | Evidence to record | If it fails |
|---|---|---|---|
| Purchase | Finish payment | Order and confirmed payment reference | Check payment status before asking for another payment |
| Download | Open delivery page and press download | Filename, edition and local file present | Distinguish expired link from a used download allowance |
| Import | Open or share the EPUB to the chosen reading app | App/version and book visible in library | Provide instructions for that app, not a second checkout link |
| Reading | Open contents, chapter and footnote | Navigation works at enlarged text | Correct the EPUB or narrow the supported-reader claim |
The distinction matters in PayRequest: opening the download landing page does not itself consume a download. The actual download action checks expiry and the download allowance. An email scanner opening the landing page is therefore different from a buyer downloading the file. This behavior was verified in PayRequest's download controller on 9 September 2026.
Give Buyers an Honest Kindle Route
Amazon offers Send to Kindle as a separate document-transfer service. Direct-sale delivery should tell a Kindle reader to follow Amazon's current supported-format and account instructions. Do not describe PayRequest's delivery email as automatic Kindle delivery or promise that every layout survives conversion.
A short instruction can say: “Download the EPUB to your device, then use your reading app's import option. For Kindle, follow Amazon's Send to Kindle instructions. If the file downloads but will not import, tell us the app/device and book edition.” Never ask for the reader's Amazon password.
Set Up the Offer and Support Boundary
Create one digital product, attach the approved file and review file-delivery settings. Rehearse the buyer route using the final artifact before announcing it. Keep the release card outside PayRequest if you use it as a support log; it is an editorial worksheet, not an automatic platform feature.
Decide how existing buyers receive material corrections and how you handle expired access. Do not promise unlimited downloads when your configured allowance is limited. Protected delivery controls access to the download; it does not prevent a recipient from copying a file they have received.
Check current PayRequest pricing before setting your margin: the Free plan has a 2% fee per successful payment, capped at €25 per transaction, with payment-provider fees separate. Start with one book and one clearly documented reader route, then expand support only after testing it.
Editorial note: this article and its illustrative cover were created with AI assistance. Product behavior was checked against the current implementation; the handoff card is an original planning template.
