---
title: "Introducing Paid and Protected Pages"
description: "Learn how LaunchFa.st helps you create authenticated and paid pages to prevent un-paid and un-authenticated access."
source: "https://www.launchfa.st/features/paid-and-protected-pages"
author: "Rishi Raj Jain"
created_at: 2024-03-14T19:01:00.000Z
---
> **Site index for agents**
> Fetch https://www.launchfa.st/llms.txt to discover every page on this site.
> Every page is also available as Markdown by appending `.md` to its URL.
LaunchFa.st comes with baked-in paid and protected page(s) to help you **prevent un-paid and un-authenticated users** access such pages. With the payment methods such as Stripe and Lemon Squeezy integrated in LaunchFa.st and authentication methods such as Google, Twitter and Credentials, such payment callbacks' and user authentication methods can be used by your system to grant access only to the paid and authenticated users to paid and protected pages in your application.
Here's how easily you can create paid and protected pages with LaunchFa.st:
- Create a file, say `paid_and_protected.astro` with the following code:
```html
---
// File: src/pages/paid_and_protected.astro
import redis from '@/lib/db/upstash'
import { getSession } from '@/lib/utils/auth'
const session: any = getSession(Astro.cookies)
if (!session) return webResponse('Unauthorized', 403, {})
if (session?.email) {
const paid = await redis.hget('access', session.email)
if (paid !== 1) return webResponse('Unauthorized', 403, {})
}
---
Paid and Protected Content!
```
- That's it! The Upstash Redis instance integrated in the LaunchFast Starter Kit takes care of fetching the user paid status and the `getSession` function takes care of decoding the user authentication status. If unauthorized or not paid, a 403 response is sent enforcing pay and authentication based access to the content.
Worry not, with LaunchFa.st you get such a page `paid_and_protected.astro` built for you with goodies on top.