DEV Community

holdi
holdi

Posted on

How to deliver digital downloads automatically with no backend

#productivity #freelancing #ai #business

You don’t need a server, Node.js, or PHP to sell digital goods. You don't need to write a script to handle file uploads, database records, or email sending. You can achieve this purely on the client side using standard web technologies and free third-party APIs.

This approach works perfectly for selling digital assets like eBooks, code templates, font packs, or UI kits. The strategy relies on the Stripe Payment Link API and a hidden <a> tag.

The Architecture

The core idea is simple. We create a client-side payment flow that redirects the user to Stripe to complete the transaction. Once Stripe redirects the user back to your page, we immediately trigger a file download.

Because this happens entirely in the browser (the user's machine), you don't need a backend to serve the file securely. You don't have to worry about server load or bandwidth throttling. Your web host handles the static file serving, which is what they are optimized for anyway.

Prerequisites

To implement this, you need three things:

  1. A Stripe Account: You need a Standard account (personal or business). Standard accounts allow you to use Webhooks and Payment Links.
  2. A Hosting Provider: You can use Netlify, Vercel, GitHub Pages, or even an old static hosting account.
  3. Your Digital File: The file (e.g., my-template.zip) must be hosted on a public URL.

Step 1: Create the Stripe Payment Link

Do not use the Stripe Dashboard to create a standard checkout page manually if you want zero backend logic. Instead, generate a Payment Link programmatically.

Log in to your Stripe dashboard and navigate to Developers > API to get your API Key. Then, make a single POST request to create a link with the "Success URL" pointing back to your own site.

curl https://api.stripe.com/v1/checkout/sessions \
  -u sk_test_YOUR_KEY: \
  -d mode='payment' \
  -d line_items[0][price_data][currency]='usd' \
  -d line_items[0][price_data][product_data][name]='UI Kit Bundle' \
  -d line_items[0][quantity]=1 \
  -d success_url='https://your-site.com/?success=true'
Enter fullscreen mode Exit fullscreen mode

This returns a JSON object containing a url. This URL is the unique checkout link for your product.

Step 2: The Client-Side Logic

On your website, place a simple button for the user to buy the item. When they click it, you use JavaScript to open the Stripe link.

function buyItem() {
  const priceId = 'price_1234567890'; // Your Stripe Price ID
  const successUrl = 'https://your-site.com/?success=true';

  const url = `https://buy.stripe.com/${priceId}?success_url=${successUrl}`;
  window.location.href = url;
}
Enter fullscreen mode Exit fullscreen mode

This sends the user to Stripe to enter payment details. Once they pay, Stripe redirects them to your-site.com?success=true.

Step 3: The "No Backend" Delivery

This is the clever part. In your HTML, create a standard link with display: none (so it doesn't clutter your UI) and an id. Point the href to your file. We will use JavaScript to click this link automatically after the user lands on the success page.

<!-- The download link, hidden from view -->
<a id="download-trigger" href="https://your-cdn.com/files/my-digital-pack.zip" style="display:none;"></a>

<script>
  // Check if the user just returned from Stripe
  const urlParams = new URLSearchParams(window.location.search);

  if (urlParams.get('success') === 'true') {
    // Trigger the hidden link to start the download
    document.getElementById('download-trigger').click();

    // Optional: Clear the URL query params
    window.history.replaceState({}, document.title, "/");
  }
</script>
Enter fullscreen mode Exit fullscreen mode

When the user lands on the success page, the script detects the success=true flag and programmatically clicks the hidden link. The browser immediately initiates the download of the ZIP file. No server code was required to serve that file to the user.

Considerations and Limitations

While this method is incredibly lightweight, it is not suitable for high-volume enterprise applications.

Security
Anyone with the URL your-site.com?success=true can technically trigger a download, provided they wait for the redirect. If you are selling high-value proprietary software, this method is less secure than a backend-protected delivery system. However, for assets like design packs, templates, and fonts where the value is in the creative work and not the source code, this frictionless method works well.

Bandwidth
Because the browser initiates the download directly, you don't consume your server's CPU or RAM resources for the file transfer. Your hosting provider simply streams the static file to the visitor.

Why This Works for Freelancers

If you are a freelancer selling UI kits or code snippets, you likely don't need a full e-commerce stack. You just need a quick, reliable way to get the file into the customer's hands.

This pattern is "Stateless." It requires no database to store a "downloaded" status because the download happens instantly upon successful redirection. It keeps your overhead low and your profits high.

I sell these kinds of digital packs in a tiny automated Telegram store - instant USDT delivery. Check it: https://t.me/m3lmhermes_bot

Top comments (0)