Member Avatar for Collection Agen

I had no idea what category to really put this in but this seemed most relevant. Please feel free to move it to the correct category.

What I wanted to do was make my guide from my site downloadable by pdf but want to make it so that when the user logs in it encrypts their download with their payment info from clickbank. I also wanted something like a password for each person unique to them like their email, or something they couldn't share it off that pc.

if you ever bought tickets online from universal studios they do something similar which is they email you a pdf of your ticket customized for you. I would like to do this or know what allows me to do this

and if this is too hard or something then what is a good editor that I can protect the document with? Like above if they could only use it on that pc then it would be awesome

  • 2 Contributors
  • 2 Replies
  • 103 Views
  • 12 Hours Discussion Span
  • Latest Post Latest Post by Collection Agen

Dani AI

Generated

As described, the goal is to give each buyer a PDF that is unique and hard to share; as pointed out, that requires server-side control. Practical, realistic tradeoffs follow: full “PC‑only” binding is possible but expensive and intrusive; a better balance is per-sale issuance + watermarking + short-lived access tokens.

A common, effective workflow

  1. After payment, create an order record with an orderID and a single-use, expiring download token.
  2. Generate the PDF on demand (server-side) and stamp it visibly with buyer info and an orderID or QR code. Invisible metadata and a hashed orderID can be added too.
  3. Serve the file only via HTTPS when the token is validated; optionally set a PDF open password and email it separately.
  4. Keep the server-side record so you can revoke a token or reissue a PDF if needed.

Minimal example (token generation)

$token = bin2hex(random_bytes(16));
storeToken($userId, $token, time() + 3600); // expires in 1 hour

Notes, cautions, and options

  • Do NOT embed full payment details (credit card numbers) in PDFs — this raises PCI and privacy issues. Use orderIDs or ClickBank transaction IDs instead.
  • PDF passwords and client-side protections are deterrents, not ironclad; many tools can remove basic PDF restrictions. Watermarks plus server-side revocation give good practical protection.
  • If absolute device-locking is required, consider a commercial PDF DRM or a native “secure viewer” that registers hardware IDs and checks a license server. That approach is more complex, costs money, and can frustrate users.

For PHP you can use server libraries (TCPDF, mPDF, wkhtmltopdf, etc.) to build and stamp PDFs. The recommended starting point is server-side generation + unique token + visible watermark; move to commercial DRM only if that level of control is truly necessary.

Recommended Answers

All 2 Replies

Member Avatar for stymiee

This definitely is not the best place for this thread as it it requires a server side language to what you want to do. What programming language will you be developing this in?

Member Avatar for Collection Agen

my guide is just made in word then i put it into html, and convert it to php right now with my current login.

I think I found a good program anyway at http://www.locklizard.com it's expensive but seems very good

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.