Purchase Flow
This guide is for a buyer using a public The Library track page. For the producer’s payment and delivery view, see Managing Sales.
Choose a licence
Section titled “Choose a licence”Review the displayed licence name, description, price, currency, deliverables, and terms. Those details are configured by the seller, so do not infer rights or included files from a licence name alone.
The Library checks that the seller can accept payment and has Dropbox delivery connected before it offers checkout. If purchases are temporarily unavailable, no payment is started and no files are copied.
Complete checkout
Section titled “Complete checkout”Enter an email address you can access and complete Stripe Checkout. Cancelling or abandoning Checkout does not start file preparation. The Library waits for Stripe’s signed payment confirmation; the browser redirect alone is not treated as payment.
After a successful payment, the return page becomes your purchase portal. You can keep it open while the files are prepared. A preparing email also contains the same portal access, so delivery does not depend on the browser remaining open.
Download the files
Section titled “Download the files”Only after payment succeeds does The Library copy the exact promised Dropbox revisions into private R2 storage. When every required file is verified, the portal changes to ready and a ready email is sent.
You can download files individually or as one ZIP. Download requests use short-lived, purchase-specific tickets; the private R2 objects and Dropbox source links are never exposed. Interrupted individual downloads support browser range/resume.
Access remains available for 30 days from the time the package becomes ready. Preparation time does not shorten that window. After expiry, downloads stop and the stored purchase files are removed.
If the email is wrong or missing
Section titled “If the email is wrong or missing”Keep the purchase reference shown in the portal or Stripe receipt. Support can use that immutable reference plus another matching purchase detail to correct the email, rotate the portal access, and resend it. Support never looks up or changes a purchase using an email address alone.
If access has expired, support can attempt to reinstate the exact originally purchased Dropbox revisions for a new 30-day window. If those exact bytes no longer exist, the producer or support team must resolve or refund the purchase rather than silently substituting a changed file.